CVE-2022-49375: rtc: mt6397: check return value after calling platform_get_resource()
In the Linux kernel, the following vulnerability has been resolved:
rtc: mt6397: check return value after calling platform_get_resource()
It will cause null-ptr-deref if platform_get_resource() returns NULL,
we need check the return value.
Security readout for executives and security teams
Plain-English summary
CVE-2022-49375 is a Linux kernel bug in the MediaTek MT6397 RTC driver. If a required hardware resource lookup fails, the kernel may dereference a NULL pointer and crash. The main business risk is local denial of service on affected systems, not data theft or privilege escalation based on the provided sources.
Executive priority
Treat as a moderate-priority availability issue. Patch through normal kernel maintenance, with faster handling for devices where local users, tenants, or apps could trigger kernel crashes.
Technical view
The rtc-mt6397 driver did not check whether platform_get_resource() returned NULL before use. The resolved change adds return-value validation to prevent a NULL pointer dereference. CVSS 3.1 is 5.5, local attack vector, low complexity, low privileges required, no user interaction, and high availability impact only.
Likely exposure
Exposure is likely limited to Linux systems running affected kernel builds with the MT6397 RTC driver relevant to their hardware. This is more plausible in embedded, mobile, or MediaTek-based environments than in generic server fleets.
Exploitation context
The source bundle marks KEV as false and provides no evidence of active exploitation. The CVSS vector requires local access with low privileges. Impact is described as availability loss through a kernel NULL pointer dereference.
Researcher notes
Evidence is narrow but consistent: the CVE record describes a missing NULL check after platform_get_resource(). The provided references are Linux stable commits. No source in the bundle claims remote exploitation, confidentiality impact, integrity impact, or public weaponization.
Mitigation direction
Apply Linux stable or distribution kernel updates containing the referenced fix.
Check vendor or distribution advisories for exact fixed package versions.
Prioritize MediaTek MT6397-based embedded or device fleets.
If updates are unavailable, request vendor mitigation guidance.
Avoid assuming a generic configuration workaround without vendor confirmation.
Validation and detection
Inventory systems for affected Linux kernel versions and MT6397 RTC driver use.
Confirm whether vendor kernels include one of the referenced stable fixes or backports.
Review crash telemetry for NULL pointer dereferences in the mt6397 RTC path.
Verify patched systems no longer carry the vulnerable driver logic.
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-476: 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.
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-476 · source CWE mapping
NULL Pointer Dereference
NULL Pointer Dereference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.