media: bttv: fix use after free error due to btv->timeout timer
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.18% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: Linux Linux 1871014d6ef4812ad11ef7d838d73ce09d632267, 20568d06f6069cb835e05eed432edf962645d226, 2f3d9198cdae1cb079ec8652f4defacd481eab2b.
Low priority for now. Upgrade to Linux Linux 1871014d6ef4812ad11ef7d838d73ce09d632267, 20568d06f6069cb835e05eed432edf962645d226, 2f3d9198cdae1cb079ec8652f4defacd481eab2b or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: media: bttv: fix use after free error due to btv->timeout timer There may be some a race condition between timer function bttv_irq_timeout and bttv_remove. The timer is setup in probe and there is no timer_delete operation in remove function. When it hit kfree btv, the function might still be invoked, which will cause use after free bug. This bug is found by static analysis, it may be false positive. Fix it by adding del_timer_sync invoking to the remove function. cpu0 cpu1 bttv_probe ->timer_setup ->bttv_set_dma ->mod_timer; bttv_remove ->kfree(btv); ->bttv_irq_timeout ->USE btv
- Published
- May 21, 2024
- Updated
- Aug 5, 2026
- EPSS
- 0.1% · 7th percentile
- CWE
- CWE-362
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.0
- CNA · Linux
- 7.8
- 0.8 point gap
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.15 and later · before 4.19.299
- linux linux kernel4.20 and later · before 5.4.261
- linux linux kernel5.5 and later · before 5.10.201
- linux linux kernel5.11 and later · before 5.15.139
- linux linux kernel5.16 and later · before 6.1.63
- linux linux kernel6.2 and later · before 6.5.12
- linux linux kernel6.6 and later · before 6.6.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.15affected
- 162e6376ac58440beb6a2d2ee294f5d88ea58dd1 and later · before bbc3b8dd2cb7817e703f112d988e4f4728f0f2a9affected · git
- 162e6376ac58440beb6a2d2ee294f5d88ea58dd1 and later · before b35fdade92c5058a5e727e233fe263b828de2c9aaffected · git
- 162e6376ac58440beb6a2d2ee294f5d88ea58dd1 and later · before 2f3d9198cdae1cb079ec8652f4defacd481eab2baffected · git
- 162e6376ac58440beb6a2d2ee294f5d88ea58dd1 and later · before 51c94256a83fe4e17406c66ff3e1ad7d242d8574affected · git
- 162e6376ac58440beb6a2d2ee294f5d88ea58dd1 and later · before 20568d06f6069cb835e05eed432edf962645d226affected · git
- 162e6376ac58440beb6a2d2ee294f5d88ea58dd1 and later · before 1871014d6ef4812ad11ef7d838d73ce09d632267affected · git
- 162e6376ac58440beb6a2d2ee294f5d88ea58dd1 and later · before 847599fffa528b2cdec4e21b6bf7586dad982132affected · git
- 162e6376ac58440beb6a2d2ee294f5d88ea58dd1 and later · before bd5b50b329e850d467e7bcc07b2b6bde3752fbdaaffected · git
- before 4.15not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:8 | bpftool | before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
| AlmaLinux:8 | kernel | before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
| AlmaLinux:8 | kernel-abi-stablelists | before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
| AlmaLinux:8 | kernel-core | before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
| AlmaLinux:8 | kernel-cross-headers | before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
| AlmaLinux:8 | kernel-debug | before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
| AlmaLinux:8 | kernel-debug-core | before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
| AlmaLinux:8 | kernel-debug-devel | before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules | before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
| AlmaLinux:8 | kernel-debug-modules-extra | before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
| AlmaLinux:8 | kernel-devel | before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
| AlmaLinux:8 | kernel-doc | before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
| AlmaLinux:8 | kernel-headers | before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
| AlmaLinux:8 | kernel-modules | before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
| AlmaLinux:8 | kernel-modules-extra | before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
| AlmaLinux:8 | kernel-tools | before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
| AlmaLinux:8 | kernel-tools-libs | before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
| AlmaLinux:8 | kernel-tools-libs-devel | before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
| AlmaLinux:8 | kernel-zfcpdump | before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
| AlmaLinux:8 | kernel-zfcpdump-core | before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
| AlmaLinux:8 | kernel-zfcpdump-devel | before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
| AlmaLinux:8 | kernel-zfcpdump-modules | before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
| AlmaLinux:8 | kernel-zfcpdump-modules-extra | before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
| AlmaLinux:8 | perf | before 4.18.0-553.16.1.el8_10 | 4.18.0-553.16.1.el8_10 |
+3
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
- CVE-2016-5195Race condition in mm/gup.c in the Linux kernel 2.x through 4.x before 4.8.3 allows local users to gain privileges by leveraging incorrect haKEV83Now
Published before and after this one in the same product
- ← EarlierCVE-2023-52845May 21, 2024 · tipc: Change nla_policy for bearer-related names to NLA_NUL_STRING22Monitor
- ← EarlierCVE-2023-52846May 21, 2024 · hsr: Prevent use after free in prp_create_tagged_frame()31Monitor
- Later →CVE-2023-52848May 21, 2024 · f2fs: fix to drop meta_inode's page cache in f2fs_put_super()22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 1871014d6ef4812ad11ef7d838d73ce09d632267 | Vendor (CNA) |
| Linux Linux | 20568d06f6069cb835e05eed432edf962645d226 | Vendor (CNA) |
| Linux Linux | 2f3d9198cdae1cb079ec8652f4defacd481eab2b | Vendor (CNA) |
| Linux Linux | 51c94256a83fe4e17406c66ff3e1ad7d242d8574 | Vendor (CNA) |
| Linux Linux | 847599fffa528b2cdec4e21b6bf7586dad982132 | Vendor (CNA) |
| Linux Linux | b35fdade92c5058a5e727e233fe263b828de2c9a | Vendor (CNA) |
| Linux Linux | bbc3b8dd2cb7817e703f112d988e4f4728f0f2a9 | Vendor (CNA) |
| Linux Linux | bd5b50b329e850d467e7bcc07b2b6bde3752fbda | Vendor (CNA) |
| almalinux:bpftool | 4.18.0-553.16.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel | 4.18.0-553.16.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-abi-stablelists | 4.18.0-553.16.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-core | 4.18.0-553.16.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-cross-headers | 4.18.0-553.16.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug | 4.18.0-553.16.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-core | 4.18.0-553.16.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-devel | 4.18.0-553.16.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-modules | 4.18.0-553.16.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-debug-modules-extra | 4.18.0-553.16.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-devel | 4.18.0-553.16.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| almalinux:kernel-doc | 4.18.0-553.16.1.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| debian:linux | 6.1.64-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')CVSS vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/20568d06f6069cb835e05eed432edf962645d226
- git.kernel.org/stable/c/2f3d9198cdae1cb079ec8652f4defacd481eab2b
- git.kernel.org/stable/c/51c94256a83fe4e17406c66ff3e1ad7d242d8574
- git.kernel.org/stable/c/847599fffa528b2cdec4e21b6bf7586dad982132
- git.kernel.org/stable/c/b35fdade92c5058a5e727e233fe263b828de2c9a
- git.kernel.org/stable/c/bbc3b8dd2cb7817e703f112d988e4f4728f0f2a9
- git.kernel.org/stable/c/bd5b50b329e850d467e7bcc07b2b6bde3752fbda
Vendor advisories and official records. Exploit/PoC links are deliberately left out.