Security readout for executives and security teams
Plain-English summary
CVE-2022-49846 is a Linux kernel memory corruption bug in the UDF filesystem code. A local, low-privileged attacker may be able to trigger an out-of-bounds kernel write, risking system compromise or crash. The public record does not show active exploitation.
Executive priority
Treat as high priority for Linux fleets with untrusted local users, shared compute, containers, or media-processing workflows. It is not shown as actively exploited, but kernel memory corruption with high impact warrants timely remediation.
Technical view
The flaw is a CWE-787 slab out-of-bounds write in udf_find_entry() during UDF name lookup. Syzbot/KASAN reported a 105-byte write beyond a kmalloc-256 object. CVSS 3.1 is 7.8 with local attack vector, low complexity, low privileges, no user interaction, and high C/I/A impact.
Likely exposure
Linux systems are relevant, especially where local users, workloads, or automation can cause the kernel to process UDF filesystems or media. Exposure depends on kernel build, distro backports, and whether the UDF code path is reachable.
Exploitation context
The evidence supports local exploitation conditions only. KEV is false in the source bundle, and no cited source here claims in-the-wild exploitation. The report came from syzbot fuzzing, not a public attack campaign.
Researcher notes
Focus analysis on fs/udf/namei.c and the udf_find_entry() copy path fixed by the stable commits. The source record gives affected upstream ranges and commit references, but distro-specific applicability requires vendor mapping.
Mitigation direction
Apply Linux kernel or distro updates containing the referenced stable UDF fixes.
Prioritize multi-user systems and hosts processing removable media or filesystem images.
Check vendor advisories because distro backports may not match upstream version numbers.
Reduce untrusted UDF filesystem handling until patched, where operationally feasible.
Validation and detection
Inventory Linux kernel versions and vendor security status for CVE-2022-49846.
Confirm the running kernel includes the relevant upstream or backported UDF fix.
Review whether UDF filesystem support is enabled and reachable on exposed hosts.
Check for local workloads that can supply or trigger UDF media processing.
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-787: 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
9Source 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-787 · source CWE mapping
Out-of-bounds Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.