CVE-2026-92483: Software Security Vulnerability Vulnerability

UNKNOWN
Advisory Identifier: GHSA-ppch-xf6h-8vx5
Share
Published
Advisory Summary

CVE-2026-92483 is a security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2026-92483 at a Glance

CVE Identifier CVE-2026-92483
GHSA Identifier GHSA-ppch-xf6h-8vx5
Severity N/A
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

How to Fix CVE-2026-92483

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2026-92483, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

In the Linux kernel, the following vulnerability has been resolved: liveupdate: Remember FLB retrieve() status LUO keeps track of successful retrieve attempts on an FLB. It does so to avoid multiple retrievals of the same FLB. Multiple retrievals cause problems because once the FLB is retrieved, the serialized data structures are likely freed and the FLB is likely in a very different state from what the code expects. All this works well when retrieve succeeds. When it fails, luo_flb_retrieve_one() returns the error immediately, without ever storing anywhere that a retrieve was attempted or what its error code was. If the user attempts to retrieve another file registered with the same FLB, LUO will attempt to call the FLB's retrieve() callback again. The retry is problematic for much of the same reasons listed above. The FLB is likely in a very different state than what the retrieve logic normally expects (e.g. some KHO pages may have already been restored and freed). There is no sane way of attempting the retrieve again. Remember the error retrieve returned and directly return it on a retry. This is done by changing the retrieved bool to a retrieve_status integer. A value of 0 means retrieve was never attempted, a positive value means it succeeded, and a negative value means it failed and the error code is the value. This is similar to commit f85b1c6af5bc ("liveupdate: luo_file: remember retrieve() status") which did the same for LUO files.

References

NVD — CVE-2026-92483 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-92483
git.kernel.org/stable/c/5c4a03afcb... WEB
https://git.kernel.org/stable/c/5c4a03afcb21783987ffc64562b76ddd5a21b12b
git.kernel.org/stable/c/908f3ea3f0... WEB
https://git.kernel.org/stable/c/908f3ea3f050b865c5c2d8c1da566185a4a3efc0

Frequently Asked Questions

What is CVE-2026-92483?
CVE-2026-92483 is a security vulnerability in Software classified as a security vulnerability vulnerability under General Security Weakness.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2026-92483?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What CWE is associated with CVE-2026-92483?
CVE-2026-92483 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2026-92483?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-ppch-xf6h-8vx5",
  "modified" : "2026-09-17T18:32:06Z",
  "published" : "2026-09-17T18:32:06Z",
  "aliases" : [ "CVE-2026-92483" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nliveupdate: Remember FLB retrieve() status\n\nLUO keeps track of successful retrieve attempts on an FLB. It does so\nto avoid multiple retrievals of the same FLB. Multiple retrievals cause\nproblems because once the FLB is retrieved, the serialized data\nstructures are likely freed and the FLB is likely in a very different\nstate from what the code expects.\n\nAll this works well when retrieve succeeds. When it fails,\nluo_flb_retrieve_one() returns the error immediately, without ever\nstoring anywhere that a retrieve was attempted or what its error code\nwas. If the user attempts to retrieve another file registered with the\nsame FLB, LUO will attempt to call the FLB's retrieve() callback again.\n\nThe retry is problematic for much of the same reasons listed above. The\nFLB is likely in a very different state than what the retrieve logic\nnormally expects (e.g. some KHO pages may have already been restored and\nfreed).\n\nThere is no sane way of attempting the retrieve again. Remember the\nerror retrieve returned and directly return it on a retry.\n\nThis is done by changing the retrieved bool to a retrieve_status\ninteger. A value of 0 means retrieve was never attempted, a positive\nvalue means it succeeded, and a negative value means it failed and the\nerror code is the value.\n\nThis is similar to commit f85b1c6af5bc (\"liveupdate: luo_file: remember\nretrieve() status\") which did the same for LUO files.",
  "severity" : [ ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-92483"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/5c4a03afcb21783987ffc64562b76ddd5a21b12b"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/908f3ea3f050b865c5c2d8c1da566185a4a3efc0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : null,
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2026-09-17T17:17:50Z"
  }
}