VulnerabilityPublished 27 Jul 2026Updated 30 Jul 2026

CVE-2026-64550: Linux kernel · net: qualcomm: rmnet: validate MAP frame length before ingress parsing

Source GCVE Database

Not known to be exploited · CVSS 7.3 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

7.3High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:H

Attack Vector: Local
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: Low
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-wpm4-rcr2-x634

What to do

AI-suggested

A fix has been implemented in the Linux kernel to validate MAP frame length on all ingress paths, including when ingress deaggregation is disabled. Users should apply the official kernel updates that include this patch. Since this is a kernel vulnerability, updating to a fixed kernel version is the recommended remediation. Patch status is not explicitly confirmed here; check the vendor or Linux kernel advisories for the specific fixed versions and apply updates accordingly.

Description

A vulnerability in the Linux kernel's Qualcomm rmnet driver was resolved that involved improper validation of MAP frame length before ingress parsing. When ingress deaggregation is disabled, the code path skipped length validation, leading to out-of-bounds reads of packet data. This could cause kernel memory corruption and potentially allow an attacker with local privileges to escalate impact. The issue was fixed by factoring out and applying length validation on all ingress paths.

Impact

This vulnerability allows an attacker with local privileges to cause out-of-bounds memory reads in kernel space, potentially leading to memory corruption. The CVSS vector indicates high confidentiality impact, low integrity impact, and high availability impact. Exploitation could result in denial of service or information disclosure. No known exploits in the wild have been reported.

Summary

The Linux kernel Qualcomm rmnet driver had a vulnerability (CVE-2026-64550) where, if ingress deaggregation was disabled, the rmnet_map_ingress_handler() function bypassed length validation performed by rmnet_map_deaggregate(). This caused the parser to dereference MAP and checksum headers based on on-wire packet length without verifying the actual skb buffer length, leading to out-of-bounds memory reads and a slab-out-of-bounds bug detected by KASAN. The fix involved refactoring the length validation into rmnet_map_validate_packet_len() and applying it to the no-aggregation ingress path to prevent processing frames shorter than the header.

References

Community reviews

Loading reviews…