CVE-2026-92483

/// Technical description

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 s

/// Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

/// References