Service interruption via leaked V4L2 entity names
Published May 1, 2024 · Updated May 12, 2026
Memory leak in the Linux kernel V4L2 mem2mem core allows local users to consume kernel memory through failed entity registration. The v4l2_m2m_register_entity function allocates entity->name but its later error-handling paths return without freeing that allocation. Reachability requires local low-privileged access and a V4L2 mem2mem registration failure; repeated failures can interrupt service by exhausting memory.
Summary
What happened
Memory leak in the Linux kernel V4L2 mem2mem core allows local users to consume kernel memory through failed entity registration. The v4l2_m2m_register_entity function allocates entity->name but its later error-handling paths return without freeing that allocation. Reachability requires local low-privileged access and a V4L2 mem2mem registration failure; repeated failures can interrupt service by exhausting memory.
The record
- CVE
- CVE-2024-27077
- Published
- May 1, 2024
- Updated
- May 12, 2026
- Vendor
- Siemens
- Product
- SIMATIC S7-1500 TM MFP - GNU/Linux subsystem
- Classifications
- CWE-20, CWE-401, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 1, 2024CVE publishedPublication date reported by the CVE source.
- May 12, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <*
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo