CVE-2022-49455: misc: ocxl: fix possible double free in ocxl_file_register_afu
In the Linux kernel, the following vulnerability has been resolved:
misc: ocxl: fix possible double free in ocxl_file_register_afu
info_release() will be called in device_unregister() when info->dev's
reference count is 0. So there is no need to call ocxl_afu_put() and
kfree() again.
Fix this by adding free_minor() and return to err_unregister error path.
Security readout for executives and security teams
Plain-English summary
CVE-2022-49455 is a Linux kernel double-free flaw in the ocxl AFU registration cleanup path. A local low-privileged user could potentially affect confidentiality, integrity, and availability on vulnerable systems. The bundle provides upstream stable fixes but does not identify affected distributions or active exploitation.
Executive priority
Treat as high priority for Linux environments where local users or shared workloads exist. The risk is lower for systems without the affected ocxl exposure, but incomplete distribution data means vulnerability management should verify vendor status promptly.
Technical view
The flaw is CWE-415 in ocxl_file_register_afu. During error cleanup, device_unregister() can already trigger info_release() when the device reference count reaches zero, so additional ocxl_afu_put() and kfree() calls can free the same object again. The fix adds free_minor() and returns through the err_unregister path.
Likely exposure
Exposure is likely limited to Linux systems running affected kernel versions with the ocxl code present and reachable by local authenticated users. The source bundle lists Linux kernel versions including 5.2 through 5.19-era entries, but downstream distro backports are not stated.
Exploitation context
The CVSS vector is local, low complexity, low privileges, no user interaction, with high impact. The bundle marks KEV as false and provides no cited evidence of active exploitation or public weaponization.
Researcher notes
Evidence supports a kernel memory-management bug fixed upstream. The source bundle does not provide proof-of-concept details, exploit telemetry, affected distribution packages, or non-Linux products. Avoid assuming exposure outside Linux ocxl-related code paths without vendor confirmation.
Mitigation direction
Apply vendor kernel updates that include the upstream ocxl double-free fix.
Check distribution advisories for backported fixes before judging by version alone.
Prioritize multi-user, shared compute, and privileged workload hosts for assessment.
If patching is delayed, request vendor-supported compensating controls.
Validation and detection
Inventory Linux kernel versions across potentially affected hosts.
Confirm whether the ocxl kernel component is present on those systems.
Map findings to vendor advisories and the listed upstream stable commits.
Verify patched builds include the referenced ocxl_file_register_afu cleanup fix.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-415: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
7Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.