Kernel memory corruption via out-of-range PID index
Published Oct 21, 2024 · Updated Aug 5, 2026
Out-of-bounds write in Linux kernel rtl2832 PID filtering allows local users to corrupt kernel memory through filter index 32. rtl2832_pid_filter accepts index 32 because its upper-bound test uses > 32, after which set_bit or clear_bit accesses beyond the 32-bit dev->filters field. Triggering the flaw requires access to an RTL2832 DVB device with hardware PID filtering, and the write can destabilize the driver or kernel.
Summary
What happened
Out-of-bounds write in Linux kernel rtl2832 PID filtering allows local users to corrupt kernel memory through filter index 32. rtl2832_pid_filter accepts index 32 because its upper-bound test uses > 32, after which set_bit or clear_bit accesses beyond the 32-bit dev->filters field. Triggering the flaw requires access to an RTL2832 DVB device with hardware PID filtering, and the write can destabilize the driver or kernel.
The record
- CVE
- CVE-2024-47698
- Published
- Oct 21, 2024
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1068
- 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=4.0
- Affected versionversion=4b01e01a81b6629878344430531ced347cc2ed5b <15bea004e939d938a6771dfcf2a26cc899ffd20a
- Affected versionversion=4b01e01a81b6629878344430531ced347cc2ed5b <49b33c38d202d3327dcfd058e27f541dcc308b92
- Affected versionversion=4b01e01a81b6629878344430531ced347cc2ed5b <527ab3eb3b0b4a6ee00e183c1de6a730239e2835
- Affected versionversion=4b01e01a81b6629878344430531ced347cc2ed5b <66dbe0df6eccc7ee53a2c35016ce81e13b3ff447
- Affected versionversion=4b01e01a81b6629878344430531ced347cc2ed5b <6ae3b9aee42616ee93c4585174f40c767828006d
- Affected versionversion=4b01e01a81b6629878344430531ced347cc2ed5b <7065c05c6d58b9b9a98127aa14e9a5ec68173918
- Affected versionversion=4b01e01a81b6629878344430531ced347cc2ed5b <8ae06f360cfaca2b88b98ca89144548b3186aab1
- Affected versionversion=4b01e01a81b6629878344430531ced347cc2ed5b <a879b6cdd48134a3d58949ea4f075c75fa2d7d71
- Affected versionversion=4b01e01a81b6629878344430531ced347cc2ed5b <bedd42e07988dbdd124b23e758ffef7a681b9c60
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