CVE-2022-49937: media: mceusb: Use new usb_control_msg_*() routines
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.18% (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 587f793c64d99d92be8ef01c4c69d885a3f2edb6, 608e58a0f4617977178131f5f68a3fce1d3f5316, 75913c562f5ba4cf397d835c63f443879167c6f6.
Low priority for now. Upgrade to Linux Linux 587f793c64d99d92be8ef01c4c69d885a3f2edb6, 608e58a0f4617977178131f5f68a3fce1d3f5316, 75913c562f5ba4cf397d835c63f443879167c6f6 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: mceusb: Use new usb_control_msg_*() routines Automatic kernel fuzzing led to a WARN about invalid pipe direction in the mceusb driver: ------------[ cut here ]------------ usb 6-1: BOGUS control dir, pipe 80000380 doesn't match bRequestType 40 WARNING: CPU: 0 PID: 2465 at drivers/usb/core/urb.c:410 usb_submit_urb+0x1326/0x1820 drivers/usb/core/urb.c:410 Modules linked in: CPU: 0 PID: 2465 Comm: kworker/0:2 Not tainted 5.19.0-rc4-00208-g69cb6c6556ad #1 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 Workqueue: usb_hub_wq hub_event RIP: 0010:usb_submit_urb+0x1326/0x1820 drivers/usb/core/urb.c:410 Code: 7c 24 40 e8 ac 23 91 fd 48 8b 7c 24 40 e8 b2 70 1b ff 45 89 e8 44 89 f1 4c 89 e2 48 89 c6 48 c7 c7 a0 30 a9 86 e8 48 07 11 02 <0f> 0b e9 1c f0 ff ff e8 7e 23 91 fd 0f b6 1d 63 22 83 05 31 ff 41 RSP: 0018:ffffc900032becf0 EFLAGS: 00010282 RAX: 0000000000000000 RBX: ffff8881100f3058 RCX: 0000000000000000 RDX: ffffc90004961000 RSI: ffff888114c6d580 RDI: fffff52000657d90 RBP: ffff888105ad90f0 R08: ffffffff812c3638 R09: 0000000000000000 R10: 0000000000000005 R11: ffffed1023504ef1 R12: ffff888105ad9000 R13: 0000000000000040 R14: 0000000080000380 R15: ffff88810ba96500 FS: 0000000000000000(0000) GS:ffff88811a800000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007ffe810bda58 CR3: 000000010b720000 CR4: 0000000000350ef0 Call Trace: <TASK> usb_start_wait_urb+0x101/0x4c0 drivers/usb/core/message.c:58 usb_internal_control_msg drivers/usb/core/message.c:102 [inline] usb_control_msg+0x31c/0x4a0 drivers/usb/core/message.c:153 mceusb_gen1_init drivers/media/rc/mceusb.c:1431 [inline] mceusb_dev_probe+0x258e/0x33f0 drivers/media/rc/mceusb.c:1807 The reason for the warning is clear enough; the driver sends an unusual read request on endpoint 0 but does not set the USB_DIR_IN bit in the bRequestType field. More importantly, the whole situation can be avoided and the driver simplified by converting it over to the relatively new usb_control_msg_recv() and usb_control_msg_send() routines. That's what this fix does.
- Published
- Jun 18, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 7th 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 kernelbefore 5.10.142
- linux linux kernel5.11 and later · before 5.15.66
- linux linux kernel5.16 and later · before 5.19.8
- linux linux kernel6.0
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
- 2.6.36affected
- 66e89522aff70fb2701ba8f6845fdcd365dd2ade and later · before 587f793c64d99d92be8ef01c4c69d885a3f2edb6affected · git
- 66e89522aff70fb2701ba8f6845fdcd365dd2ade and later · before 75913c562f5ba4cf397d835c63f443879167c6f6affected · git
- 66e89522aff70fb2701ba8f6845fdcd365dd2ade and later · before d69c738ac9310b56e84c51c8f09fc018a8291bc6affected · git
- 66e89522aff70fb2701ba8f6845fdcd365dd2ade and later · before 608e58a0f4617977178131f5f68a3fce1d3f5316affected · git
- before 2.6.36not affected · semver
- 5.10.142 and later · up to and including 5.10.*not affected · semver
- 5.15.66 and later · up to and including 5.15.*not affected · semver
- 5.19.8 and later · up to and including 5.19.*not affected · semver
- 6.0 and laternot affected · original_commit_for_fix
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 5.19.11-1 | 5.19.11-1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | kernel-64kb | before 5.14.21-150400.24.170.2 | 5.14.21-150400.24.170.2 |
| SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | kernel-docs | before 5.14.21-150400.24.170.1 | 5.14.21-150400.24.170.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | kernel-obs-build | before 5.14.21-150400.24.170.2 | 5.14.21-150400.24.170.2 |
| SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | kernel-source | before 5.14.21-150400.24.170.1 | 5.14.21-150400.24.170.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | kernel-syms | before 5.14.21-150400.24.170.1 | 5.14.21-150400.24.170.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | kernel-64kb | before 5.14.21-150500.55.113.1 | 5.14.21-150500.55.113.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | kernel-docs | before 5.14.21-150500.55.113.1 | 5.14.21-150500.55.113.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | kernel-obs-build | before 5.14.21-150500.55.113.1 | 5.14.21-150500.55.113.1 |
| SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | kernel-syms | before 5.14.21-150500.55.113.1 | 5.14.21-150500.55.113.1 |
| SUSE:Linux Enterprise Live Patching 15 SP3 | kernel-default | before 5.3.18-150300.59.211.1 | 5.3.18-150300.59.211.1 |
| SUSE:Linux Enterprise Live Patching 15 SP3 | kernel-livepatch-SLE15-SP3_Update_59 | before 1-150300.7.3.1 | 1-150300.7.3.1 |
| SUSE:Linux Enterprise Live Patching 15 SP5 | kernel-livepatch-SLE15-SP5_Update_28 | before 1-150500.11.3.1 | 1-150500.11.3.1 |
| SUSE:Linux Enterprise Micro 5.1 | kernel-rt | before 5.3.18-150300.214.1 | 5.3.18-150300.214.1 |
| SUSE:Linux Enterprise Micro 5.1 | kernel-source-rt | before 5.3.18-150300.214.1 | 5.3.18-150300.214.1 |
| SUSE:Linux Enterprise Micro 5.3 | kernel-default | before 5.14.21-150400.24.170.2 | 5.14.21-150400.24.170.2 |
| SUSE:Linux Enterprise Micro 5.3 | kernel-default-base | before 5.14.21-150400.24.170.2.150400.24.86.2 | 5.14.21-150400.24.170.2.150400.24.86.2 |
| SUSE:Linux Enterprise Micro 5.3 | kernel-rt | before 5.14.21-150400.15.124.1 | 5.14.21-150400.15.124.1 |
| SUSE:Linux Enterprise Micro 5.3 | kernel-source-rt | before 5.14.21-150400.15.124.1 | 5.14.21-150400.15.124.1 |
| SUSE:Linux Enterprise Micro 5.5 | kernel-default | before 5.14.21-150500.55.113.1 | 5.14.21-150500.55.113.1 |
| SUSE:Linux Enterprise Micro 5.5 | kernel-default-base | before 5.14.21-150500.55.113.1.150500.6.53.1 | 5.14.21-150500.55.113.1.150500.6.53.1 |
| SUSE:Linux Enterprise Micro 5.5 | kernel-rt | before 5.14.21-150500.13.100.2 | 5.14.21-150500.13.100.2 |
| SUSE:Linux Enterprise Micro 5.5 | kernel-source | before 5.14.21-150500.55.113.1 | 5.14.21-150500.55.113.1 |
| SUSE:Linux Enterprise Micro 5.5 | kernel-source-rt | before 5.14.21-150500.13.100.1 | 5.14.21-150500.13.100.1 |
+16
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- 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
Published before and after this one in the same product
- ← EarlierCVE-2022-49935Jun 18, 2025 · dma-buf/dma-resv: check if the new fence is really later31Monitor
- ← EarlierCVE-2022-49936Jun 18, 2025 · USB: core: Prevent nested device-reset calls22Monitor
- Later →CVE-2022-49938Jun 18, 2025 · cifs: fix small mempool leak in SMB2_negotiate()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 | 587f793c64d99d92be8ef01c4c69d885a3f2edb6 | Vendor (CNA) |
| Linux Linux | 608e58a0f4617977178131f5f68a3fce1d3f5316 | Vendor (CNA) |
| Linux Linux | 75913c562f5ba4cf397d835c63f443879167c6f6 | Vendor (CNA) |
| Linux Linux | d69c738ac9310b56e84c51c8f09fc018a8291bc6 | Vendor (CNA) |
| debian:linux | 5.19.11-1 · Debian:12 | Package registry (OSV) |
| suse:kernel-64kb | 5.14.21-150500.55.113.1 · SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | Package registry (OSV) |
| suse:kernel-default | 5.14.21-150500.55.113.1 · SUSE:Linux Enterprise Micro 5.5 | Package registry (OSV) |
| suse:kernel-default-base | 5.14.21-150500.55.113.1.150500.6.53.1 · SUSE:Linux Enterprise Micro 5.5 | Package registry (OSV) |
| suse:kernel-docs | 5.14.21-150500.55.113.1 · SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | Package registry (OSV) |
| suse:kernel-ec2 | 3.0.101-108.186.1 · SUSE:Linux Enterprise Server 11 SP4 LTSS EXTREME CORE | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP3_Update_59 | 1-150300.7.3.1 · SUSE:Linux Enterprise Live Patching 15 SP3 | Package registry (OSV) |
| suse:kernel-livepatch-SLE15-SP5_Update_28 | 1-150500.11.3.1 · SUSE:Linux Enterprise Live Patching 15 SP5 | Package registry (OSV) |
| suse:kernel-obs-build | 5.14.21-150500.55.113.1 · SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | Package registry (OSV) |
| suse:kernel-preempt | 5.3.18-150300.59.211.1 · SUSE:Linux Enterprise Server 15 SP3-LTSS | Package registry (OSV) |
| suse:kernel-source | 5.14.21-150500.55.113.1 · SUSE:Linux Enterprise Micro 5.5 | Package registry (OSV) |
| suse:kernel-syms | 5.14.21-150500.55.113.1 · SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | Package registry (OSV) |
| suse:kernel-zfcpdump | 5.14.21-150500.55.113.1 · SUSE:Linux Enterprise Server 15 SP5-LTSS | 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.
No history yet (it accumulates with the daily EPSS job).
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 (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.