media: radio-shark: Add endpoint checks
Noroxi assessment
Priority: Monitor (action score 22/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.15% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 2b580d0f03c4fc00013cd08f9ed96b87a08fd0d9, 3ed6a312ac1e7278f92b1b3d95377b335ae21e89, 4c3057a1927fa0b9ed8948b6f3b56b4ff9fa63d3.
Low priority for now. Upgrade to Linux Linux 2b580d0f03c4fc00013cd08f9ed96b87a08fd0d9, 3ed6a312ac1e7278f92b1b3d95377b335ae21e89, 4c3057a1927fa0b9ed8948b6f3b56b4ff9fa63d3 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: radio-shark: Add endpoint checks The syzbot fuzzer was able to provoke a WARNING from the radio-shark2 driver: ------------[ cut here ]------------ usb 1-1: BOGUS urb xfer, pipe 1 != type 3 WARNING: CPU: 0 PID: 3271 at drivers/usb/core/urb.c:504 usb_submit_urb+0xed2/0x1880 drivers/usb/core/urb.c:504 Modules linked in: CPU: 0 PID: 3271 Comm: kworker/0:3 Not tainted 6.1.0-rc4-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 Workqueue: usb_hub_wq hub_event RIP: 0010:usb_submit_urb+0xed2/0x1880 drivers/usb/core/urb.c:504 Code: 7c 24 18 e8 00 36 ea fb 48 8b 7c 24 18 e8 36 1c 02 ff 41 89 d8 44 89 e1 4c 89 ea 48 89 c6 48 c7 c7 a0 b6 90 8a e8 9a 29 b8 03 <0f> 0b e9 58 f8 ff ff e8 d2 35 ea fb 48 81 c5 c0 05 00 00 e9 84 f7 RSP: 0018:ffffc90003876dd0 EFLAGS: 00010282 RAX: 0000000000000000 RBX: 0000000000000003 RCX: 0000000000000000 RDX: ffff8880750b0040 RSI: ffffffff816152b8 RDI: fffff5200070edac RBP: ffff8880172d81e0 R08: 0000000000000005 R09: 0000000000000000 R10: 0000000080000000 R11: 0000000000000000 R12: 0000000000000001 R13: ffff8880285c5040 R14: 0000000000000002 R15: ffff888017158200 FS: 0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007ffe03235b90 CR3: 000000000bc8e000 CR4: 00000000003506f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> usb_start_wait_urb+0x101/0x4b0 drivers/usb/core/message.c:58 usb_bulk_msg+0x226/0x550 drivers/usb/core/message.c:387 shark_write_reg+0x1ff/0x2e0 drivers/media/radio/radio-shark2.c:88 ... The problem was caused by the fact that the driver does not check whether the endpoints it uses are actually present and have the appropriate types. This can be fixed by adding a simple check of these endpoints (and similarly for the radio-shark driver).
- Published
- Oct 7, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 4th percentile
- CWE
- —
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
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 kernel3.6 and later · before 4.14.316
- linux linux kernel4.15 and later · before 4.19.284
- linux linux kernel4.20 and later · before 5.4.244
- linux linux kernel5.5 and later · before 5.10.181
- linux linux kernel5.11 and later · before 5.15.114
- linux linux kernel5.16 and later · before 6.1.31
- linux linux kernel6.2 and later · before 6.3.5
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
- 3.6affected
- 8e2ce73e932b629c3e12546e5fffac7ee54d0093 and later · before 3ed6a312ac1e7278f92b1b3d95377b335ae21e89affected · git
- 8e2ce73e932b629c3e12546e5fffac7ee54d0093 and later · before afd72825b4fcb7ae4015e1c93b054f4c37a25684affected · git
- 8e2ce73e932b629c3e12546e5fffac7ee54d0093 and later · before 2b580d0f03c4fc00013cd08f9ed96b87a08fd0d9affected · git
- 8e2ce73e932b629c3e12546e5fffac7ee54d0093 and later · before 8a30dce9d7f70f8438956f6a01142b926c301334affected · git
- 8e2ce73e932b629c3e12546e5fffac7ee54d0093 and later · before b1bde4b4360c3d8a35504443efabd3243b802805affected · git
- 8e2ce73e932b629c3e12546e5fffac7ee54d0093 and later · before 53764a17f5d8f0d00b13297d06b5e65fa844288baffected · git
- 8e2ce73e932b629c3e12546e5fffac7ee54d0093 and later · before 4c3057a1927fa0b9ed8948b6f3b56b4ff9fa63d3affected · git
- 8e2ce73e932b629c3e12546e5fffac7ee54d0093 and later · before 76e31045ba030e94e72105c01b2e98f543d175acaffected · git
- before 3.6not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.37-1 | 6.1.37-1 |
| Debian:13 | linux | before 6.3.7-1 | 6.3.7-1 |
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
- CVE-2019-13272In the Linux kernel before 5.1.17, ptrace_link in kernel/ptrace.c mishandles the recording of the credentials of a process that wants to creKEV77This week
- CVE-2013-6282The (1) get_user and (2) put_user API functions in the Linux kernel before 3.5.5 on the v6k and v7 ARM platforms do not validate certain addKEV77This week
- CVE-2013-2094The perf_swevent_init function in kernel/events/core.c in the Linux kernel before 3.8.9 uses an incorrect integer data type, which allows loKEV77This week
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 | 2b580d0f03c4fc00013cd08f9ed96b87a08fd0d9 | Vendor (CNA) |
| Linux Linux | 3ed6a312ac1e7278f92b1b3d95377b335ae21e89 | Vendor (CNA) |
| Linux Linux | 4c3057a1927fa0b9ed8948b6f3b56b4ff9fa63d3 | Vendor (CNA) |
| Linux Linux | 53764a17f5d8f0d00b13297d06b5e65fa844288b | Vendor (CNA) |
| Linux Linux | 76e31045ba030e94e72105c01b2e98f543d175ac | Vendor (CNA) |
| Linux Linux | 8a30dce9d7f70f8438956f6a01142b926c301334 | Vendor (CNA) |
| Linux Linux | afd72825b4fcb7ae4015e1c93b054f4c37a25684 | Vendor (CNA) |
| Linux Linux | b1bde4b4360c3d8a35504443efabd3243b802805 | Vendor (CNA) |
| debian:linux | 6.1.37-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.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
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/3ed6a312ac1e7278f92b1b3d95377b335ae21e89
- git.kernel.org/stable/c/4c3057a1927fa0b9ed8948b6f3b56b4ff9fa63d3
- git.kernel.org/stable/c/53764a17f5d8f0d00b13297d06b5e65fa844288b
- git.kernel.org/stable/c/76e31045ba030e94e72105c01b2e98f543d175ac
- git.kernel.org/stable/c/8a30dce9d7f70f8438956f6a01142b926c301334
- git.kernel.org/stable/c/afd72825b4fcb7ae4015e1c93b054f4c37a25684
- git.kernel.org/stable/c/b1bde4b4360c3d8a35504443efabd3243b802805
Vendor advisories and official records. Exploit/PoC links are deliberately left out.