CVE-2022-48777: mtd: parsers: qcom: Fix kernel panic on skipped partition
In the Linux kernel, the following vulnerability has been resolved:
mtd: parsers: qcom: Fix kernel panic on skipped partition
In the event of a skipped partition (case when the entry name is empty)
the kernel panics in the cleanup function as the name entry is NULL.
Rework the parser logic by first checking the real partition number and
then allocate the space and set the data for the valid partitions.
The logic was also fundamentally wrong as with a skipped partition, the
parts number returned was incorrect by not decreasing it for the skipped
partitions.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can cause a kernel panic when the Qualcomm MTD partition parser encounters an empty partition name. For affected systems, the business impact is availability disruption, especially on embedded or appliance-style Linux devices using Qualcomm flash partition layouts.
Executive priority
Treat as a targeted availability risk. Patch during normal kernel maintenance unless exposed devices depend on Qualcomm MTD parsing for critical operations, where earlier remediation is justified.
Technical view
CVE-2022-48777 fixes faulty Qualcomm MTD parser cleanup and partition counting logic. A skipped partition with an empty entry name leaves a NULL name pointer, which can trigger a kernel panic during cleanup. The fix validates real partition count before allocation and setup.
Likely exposure
Likely limited to Linux systems using the Qualcomm MTD partition parser, commonly embedded or device firmware contexts. Exposure depends on kernel version, downstream vendor backports, and whether relevant flash partition data is parsed.
Exploitation context
The provided sources do not report active exploitation, KEV listing, CVSS, or public weaponization. Evidence supports a denial-of-service style kernel panic condition, not data theft or privilege escalation.
Researcher notes
The source bundle lacks CVSS, CWE, exploit prerequisites, and vendor-specific package mappings. Analysis should stay tied to kernel version lineage, parser reachability, and whether stable commits are present in downstream trees.
Mitigation direction
Update to a vendor kernel containing the referenced stable fixes.
Check Linux distribution or device vendor advisories for backported patches.
Prioritize embedded Qualcomm-based systems using MTD partition parsing.
Avoid accepting untrusted firmware or flash partition metadata until patched.
Validation and detection
Inventory affected Linux kernel versions and downstream vendor build numbers.
Confirm whether the Qualcomm MTD parser is present and used.
Check vendor changelogs for CVE-2022-48777 or referenced commits.
Review crash reports for kernel panics during MTD partition parsing.
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-48777 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.