Security readout for executives and security teams
Plain-English summary
A Linux TCP receive zero-copy flaw can mishandle file-backed memory pages and crash the kernel. A local, low-privileged user may trigger it without user interaction, potentially disrupting affected servers or workloads. The supplied evidence confirms a kernel panic, but not data theft or code execution.
Executive priority
Treat as a high-priority kernel maintenance issue, especially on systems allowing untrusted local users or workloads. Accelerate normal patching, but the supplied evidence does not justify claiming an active exploitation emergency.
Technical view
TCP receive zero-copy could map compound or filesystem-owned pages because can_map_frag() lacked required sanity checks. syzbot reproduced a panic by sending ext4-backed pages through loopback TCP using sendfile. The kernel fix rejects compound pages and requires page->mapping to be NULL.
Likely exposure
Exposure concerns Linux systems within the cited affected version ranges where a local low-privileged account can access the relevant TCP receive zero-copy behavior. Internet reachability alone is insufficient because the CVSS vector specifies local attack access.
Exploitation context
The supplied record is not in CISA KEV and provides no evidence of active exploitation. It documents a syzbot-generated local reproducer causing a kernel panic. CVSS 3.1 scores it 7.8 with low complexity, low privileges, and no user interaction.
Researcher notes
No CWE is supplied. The demonstrated outcome is a kernel panic involving ext4-backed pages entering TCP receive zero-copy. Although the CVSS vector assigns high confidentiality, integrity, and availability impacts, the bundle does not independently demonstrate data disclosure, modification, privilege escalation, or arbitrary code execution.
Mitigation direction
- Install a vendor-supported kernel release containing the applicable referenced stable fix.
- Reboot affected systems so the corrected kernel becomes active.
- If patching is delayed, restrict untrusted local access and consult vendor guidance for supported workarounds.
- Prioritize shared, multi-user, and untrusted-workload Linux hosts.
Validation and detection
- Inventory active kernel versions and compare them with vendor advisories and the CVE record.
- Confirm the running kernel contains the applicable referenced stable commit.
- Verify the corrected kernel is active after reboot, not merely installed.
- Review kernel logs and crash records for related TCP zero-copy panics.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2024-26640 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9LinuxVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://git.kernel.org/stable/c/f48bf9a83b1666d934247cb58a9887d7b3127b6fCVE reference, Linux
- https://git.kernel.org/stable/c/718f446e60316bf606946f7f42367d691d21541eCVE reference, Linux
- https://git.kernel.org/stable/c/b383d4ea272fe5795877506dcce5aad1f6330e5eCVE reference, Linux
- https://git.kernel.org/stable/c/d15cc0f66884ef2bed28c7ccbb11c102aa3a0760CVE reference, Linux
- https://git.kernel.org/stable/c/1b8adcc0e2c584fec778add7777fe28e20781e60CVE reference, Linux
- https://git.kernel.org/stable/c/577e4432f3ac810049cb7e6b71f4d96ec7c6e894CVE reference, Linux
- https://lists.debian.org/debian-lts-announce/2024/06/msg00017.htmlCVE reference, CVE · x_transferred
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.