LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53644: media: radio-shark: Add endpoint checks

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).

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This Linux kernel issue affects the radio-shark USB radio drivers. A malformed or unexpected USB device shape could trigger a kernel warning because the driver trusted endpoint layout without checking it first. The source shows a fuzzing-triggered warning, not confirmed real-world compromise or data theft.

Executive priority

Treat as routine kernel hygiene unless your environment permits untrusted USB devices on Linux systems. Patch through normal kernel maintenance, with higher priority for shared workstations, labs, or virtualization environments exposing USB devices.

Technical view

The radio-shark and radio-shark2 media drivers failed to confirm required USB endpoints existed and had appropriate types before submitting URBs. syzbot triggered a usb_submit_urb warning through an endpoint type mismatch. Kernel stable commits add endpoint validation checks.

Likely exposure

Exposure appears limited to Linux systems running affected kernel versions with the radio-shark or radio-shark2 USB media drivers available and relevant USB device interaction possible.

Exploitation context

The source describes syzbot fuzzing, and KEV is false. No cited source reports active exploitation, exploit availability, privilege escalation, or remote network reachability.

Researcher notes

Evidence is narrow: a kernel warning from missing USB endpoint validation. The record does not provide CVSS, CWE, full impact, or proof of real-world exploitation. Analysis should stay scoped to driver robustness and USB-device-triggered exposure.

Mitigation direction

  • Apply a Linux stable kernel update containing the referenced endpoint-check commits.
  • Check your Linux distribution advisory for packaged fixed kernel versions.
  • Prioritize systems where untrusted USB devices can be attached.
  • Reduce access to physical or virtual USB attachment where patching is delayed.

Validation and detection

  • Identify running kernel versions and compare them with affected and fixed vendor packages.
  • Check whether radio-shark or radio-shark2 drivers are present or loadable.
  • Confirm the deployed kernel includes the referenced stable fixes.
  • Review kernel logs for radio-shark USB warnings on relevant hosts.
Prepared
Confidence
medium
Sources
10

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-53644 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
9Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux8e2ce73e932b629c3e12546e5fffac7ee54d0093, 8e2ce73e932b629c3e12546e5fffac7ee54d0093, 8e2ce73e932b629c3e12546e5fffac7ee54d0093, 8e2ce73e932b629c3e12546e5fffac7ee54d0093, 8e2ce73e932b629c3e12546e5fffac7ee54d0093, 8e2ce73e932b629c3e12546e5fffac7ee54d0093, 8e2ce73e932b629c3e12546e5fffac7ee54d0093, 8e2ce73e932b629c3e12546e5fffac7ee54d0093unaffected
LinuxLinux3.6, 0, 4.14.316, 4.19.284, 5.4.244, 5.10.181, 5.15.114, 6.1.31, 6.3.5, 6.4affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.