Kernel memory corruption via PID-filter index 32
Published Oct 21, 2024 · Updated Aug 5, 2026
Out-of-bounds write in the Linux rtl2830 DVB frontend allows local users to corrupt kernel memory through PID-filter index 32. The rtl2830_pid_filter function accepts index 32, then set_bit or clear_bit writes a nonexistent 33rd bit past the 32-bit dev->filters field. Reachability requires local access to a system using the rtl2830 frontend and the ability to submit PID-filter controls; the record establishes memory corruption but no demonstrated exploit consequence.
Summary
What happened
Out-of-bounds write in the Linux rtl2830 DVB frontend allows local users to corrupt kernel memory through PID-filter index 32. The rtl2830_pid_filter function accepts index 32, then set_bit or clear_bit writes a nonexistent 33rd bit past the 32-bit dev->filters field. Reachability requires local access to a system using the rtl2830 frontend and the ability to submit PID-filter controls; the record establishes memory corruption but no demonstrated exploit consequence.
The record
- CVE
- CVE-2024-47697
- Published
- Oct 21, 2024
- Updated
- Aug 5, 2026
- Vendor
- Siemens
- Product
- SIMATIC S7-1500 TM MFP - GNU/Linux subsystem
- Classifications
- CWE-787, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 21, 2024CVE publishedPublication date reported by the CVE source.
- Aug 5, 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.
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