In the Linux kernel, the following vulnerability has been resolved:
media: vivid: fix compose size exceed boundary
syzkaller found a bug:
BUG: unable to handle page fault for address: ffffc9000a3b1000
#PF: supervisor write access in kernel mode
#PF: error_code(0x0002) - not-present page
PGD 100000067 P4D 100000067 PUD 10015f067 PMD 1121ca067 PTE 0
Oops: 0002 [#1] PREEMPT SMP
CPU: 0 PID: 23489 Comm: vivid-000-vid-c Not tainted 6.1.0-rc1+ #512
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014
RIP: 0010:memcpy_erms+0x6/0x10
[...]
Call Trace:
<TASK>
? tpg_fill_plane_buffer+0x856/0x15b0
vivid_fillbuff+0x8ac/0x1110
vivid_thread_vid_cap_tick+0x361/0xc90
vivid_thread_vid_cap+0x21a/0x3a0
kthread+0x143/0x180
ret_from_fork+0x1f/0x30
</TASK>
This is because we forget to check boundary after adjust compose->height
int V4L2_SEL_TGT_CROP case. Add v4l2_rect_map_inside() to fix this problem
for this case.
Security readout for executives and security teams
Plain-English summary
CVE-2022-48945 is a Linux kernel flaw in the vivid media driver. A boundary check was missing after compose height adjustment, causing a kernel page fault in testing. The available sources do not provide CVSS severity or evidence of real-world exploitation.
Executive priority
Track as a kernel maintenance issue until vendor severity is clarified. Prioritize patching where media test drivers are enabled, but do not treat it as confirmed active exploitation based on the supplied evidence.
Technical view
The issue affects the Linux kernel media vivid path. In the V4L2_SEL_TGT_CROP case, compose height could exceed bounds before buffer filling, leading to supervisor write page fault during memcpy. The fix adds v4l2_rect_map_inside() boundary handling.
Likely exposure
Exposure is most relevant to Linux systems running affected kernel versions with the vivid media driver present and usable. The source lists affected Linux versions including 3.18 through 6.2, but distribution backports may change package-level exposure.
Exploitation context
The cited evidence is a syzkaller-discovered kernel crash trace. KEV is false, and the source bundle provides no public exploitation evidence, no exploit maturity detail, and no confirmed attacker scenario.
Researcher notes
The source data is limited to the kernel fix narrative, affected version list, and stable commit references. No CVSS, CWE, attacker prerequisites, or exploitability analysis is supplied, so validation should focus on kernel provenance and driver reachability.
Mitigation direction
Apply a Linux kernel update containing the referenced stable fix commits.
Check distribution vendor advisories for backported fixed kernel packages.
Prioritize systems where the vivid media driver is built, loaded, or accessible.
If vivid is unnecessary, follow vendor-supported guidance to reduce or remove exposure.
Validation and detection
Inventory Linux kernel versions against vendor fixed package guidance.
Check whether the vivid media driver is enabled, available, or loaded.
Confirm deployed kernels include one of the referenced stable fixes or equivalent backport.
Review kernel logs for related vivid crashes, without treating logs as proof of exploitation.
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.
cve · low confidence lookup
CVE-2022-48945 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.