CVE-2022-48772: media: lgdt3306a: Add a check against null-pointer-def
In the Linux kernel, the following vulnerability has been resolved:
media: lgdt3306a: Add a check against null-pointer-def
The driver should check whether the client provides the platform_data.
The following log reveals it:
[ 29.610324] BUG: KASAN: null-ptr-deref in kmemdup+0x30/0x40
[ 29.610730] Read of size 40 at addr 0000000000000000 by task bash/414
[ 29.612820] Call Trace:
[ 29.613030] <TASK>
[ 29.613201] dump_stack_lvl+0x56/0x6f
[ 29.613496] ? kmemdup+0x30/0x40
[ 29.613754] print_report.cold+0x494/0x6b7
[ 29.614082] ? kmemdup+0x30/0x40
[ 29.614340] kasan_report+0x8a/0x190
[ 29.614628] ? kmemdup+0x30/0x40
[ 29.614888] kasan_check_range+0x14d/0x1d0
[ 29.615213] memcpy+0x20/0x60
[ 29.615454] kmemdup+0x30/0x40
[ 29.615700] lgdt3306a_probe+0x52/0x310
[ 29.616339] i2c_device_probe+0x951/0xa90
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel bug in the lgdt3306a media driver. If the driver is probed without expected platform_data, the kernel can dereference a null pointer and crash. The public bundle does not show remote exploitation, active exploitation, or broad business impact beyond systems using this specific driver path.
Executive priority
Handle through normal kernel patch management unless the organization operates affected media or embedded Linux systems. There is no source-backed evidence of active exploitation, but kernel crash conditions still matter for reliability-sensitive environments.
Technical view
The flaw is a null pointer dereference in lgdt3306a_probe, observed through KASAN at kmemdup during i2c_device_probe. The kernel fix adds a check that platform_data exists before copying it. Affected Linux kernel versions are listed in the CVE bundle, with stable kernel commit references provided.
Likely exposure
Exposure appears limited to Linux systems running affected kernels with the lgdt3306a media driver present and a probe path where client platform_data is missing. General servers without this media hardware or driver path are less likely to be exposed based on the bundle.
Exploitation context
The bundle marks KEV as false and provides no evidence of active exploitation. The available evidence is a kernel crash log, not a public exploit report. Treat this as a potential local or device-triggered denial-of-service condition unless vendor guidance says otherwise.
Researcher notes
The evidence points to missing input validation for client platform_data in the lgdt3306a probe routine. The source bundle does not provide CVSS, CWE, exploit prerequisites, or a complete version-range interpretation, so validation should rely on kernel branch advisories and the referenced commits.
Mitigation direction
Update affected Linux kernels to builds containing the referenced stable fixes.
Check distribution advisories for backported fixes matching your deployed kernel branch.
Disable or avoid loading the lgdt3306a driver where it is not required.
Prioritize systems that use media, tuner, or embedded hardware paths involving this driver.
Validation and detection
Inventory kernel versions and compare them with the CVE bundle affected entries.
Check whether the lgdt3306a driver is built, loaded, or packaged on target systems.
Review vendor kernel changelogs for the referenced stable commit IDs.
Confirm patched systems no longer include the vulnerable lgdt3306a_probe behavior.
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-48772 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.