Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-48760: USB: core: Fix hang in usb_kill_urb by adding memory barriers

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. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 26fbe9772b8c459687930511444ce443011f86bf, 546ba238535d925254e0b3f12012a5c55801e2f3, 5904dfd3ddaff3bf4a41c3baf0a8e8f31ed4599b.

Low priority for now. Upgrade to Linux Linux 26fbe9772b8c459687930511444ce443011f86bf, 546ba238535d925254e0b3f12012a5c55801e2f3, 5904dfd3ddaff3bf4a41c3baf0a8e8f31ed4599b 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: USB: core: Fix hang in usb_kill_urb by adding memory barriers The syzbot fuzzer has identified a bug in which processes hang waiting for usb_kill_urb() to return. It turns out the issue is not unlinking the URB; that works just fine. Rather, the problem arises when the wakeup notification that the URB has completed is not received. The reason is memory-access ordering on SMP systems. In outline form, usb_kill_urb() and __usb_hcd_giveback_urb() operating concurrently on different CPUs perform the following actions: CPU 0 CPU 1 ---------------------------- --------------------------------- usb_kill_urb(): __usb_hcd_giveback_urb(): ... ... atomic_inc(&urb->reject); atomic_dec(&urb->use_count); ... ... wait_event(usb_kill_urb_queue, atomic_read(&urb->use_count) == 0); if (atomic_read(&urb->reject)) wake_up(&usb_kill_urb_queue); Confining your attention to urb->reject and urb->use_count, you can see that the overall pattern of accesses on CPU 0 is: write urb->reject, then read urb->use_count; whereas the overall pattern of accesses on CPU 1 is: write urb->use_count, then read urb->reject. This pattern is referred to in memory-model circles as SB (for "Store Buffering"), and it is well known that without suitable enforcement of the desired order of accesses -- in the form of memory barriers -- it is entirely possible for one or both CPUs to execute their reads ahead of their writes. The end result will be that sometimes CPU 0 sees the old un-decremented value of urb->use_count while CPU 1 sees the old un-incremented value of urb->reject. Consequently CPU 0 ends up on the wait queue and never gets woken up, leading to the observed hang in usb_kill_urb(). The same pattern of accesses occurs in usb_poison_urb() and the failure pathway of usb_hcd_submit_urb(). The problem is fixed by adding suitable memory barriers. To provide proper memory-access ordering in the SB pattern, a full barrier is required on both CPUs. The atomic_inc() and atomic_dec() accesses themselves don't provide any memory ordering, but since they are present, we can use the optimized smp_mb__after_atomic() memory barrier in the various routines to obtain the desired effect. This patch adds the necessary memory barriers.

HighCVSS 7.1 · v3.1—No exploit Fix available
Published
Jun 20, 2024
Updated
Jun 17, 2026
EPSS
0.1% · 8th percentile

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.1 / 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.

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.

Follow CVE-2022-48760

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

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 help

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

VendorProduct
linuxlinux 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 4.4.302
  • linux linux kernel4.5 and later · before 4.9.300
  • linux linux kernel4.10 and later · before 4.14.265
  • linux linux kernel4.15 and later · before 4.19.228
  • linux linux kernel4.20 and later · before 5.4.176
  • linux linux kernel5.5 and later · before 5.10.96
  • linux linux kernel5.11 and later · before 5.15.19
  • linux linux kernel5.16 and later · before 5.16.5
  • linux linux kernel5.17

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.29affected
    • 49367d8f1d9f26482cf7089489e90f0afd0a942c and later · before 5f138ef224dffd15d5e5c5b095859719e0038427affected · git
    • 49367d8f1d9f26482cf7089489e90f0afd0a942c and later · before b50f5ca60475710bbc9a3af32fbfc17b1e69c2f0affected · git
    • 49367d8f1d9f26482cf7089489e90f0afd0a942c and later · before 546ba238535d925254e0b3f12012a5c55801e2f3affected · git
    • 49367d8f1d9f26482cf7089489e90f0afd0a942c and later · before 5904dfd3ddaff3bf4a41c3baf0a8e8f31ed4599baffected · git
    • 49367d8f1d9f26482cf7089489e90f0afd0a942c and later · before 9c61fce322ac2ef7fecf025285353570d60e41d6affected · git
    • 49367d8f1d9f26482cf7089489e90f0afd0a942c and later · before e3b131e30e612ff0e32de6c1cb4f69f89db29193affected · git
    • 49367d8f1d9f26482cf7089489e90f0afd0a942c and later · before 9340226388c66a7e090ebb00e91ed64a753b6c26affected · git
    • 49367d8f1d9f26482cf7089489e90f0afd0a942c and later · before c9a18f7c5b071dce5e6939568829d40994866ab0affected · git
    • 49367d8f1d9f26482cf7089489e90f0afd0a942c and later · before 26fbe9772b8c459687930511444ce443011f86bfaffected · git

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 5.16.7-15.16.7-1
SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSkernel-default-basebefore 5.3.18-150200.24.197.1.150200.9.101.15.3.18-150200.24.197.1.150200.9.101.1
SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSkernel-docsbefore 5.3.18-150200.24.197.15.3.18-150200.24.197.1
SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSkernel-obs-buildbefore 5.3.18-150200.24.197.15.3.18-150200.24.197.1
SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSkernel-preemptbefore 5.3.18-150200.24.197.15.3.18-150200.24.197.1
SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSkernel-sourcebefore 5.3.18-150200.24.197.15.3.18-150200.24.197.1
SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSkernel-symsbefore 5.3.18-150200.24.197.15.3.18-150200.24.197.1
SUSE:Linux Enterprise Live Patching 15 SP2kernel-defaultbefore 5.3.18-150200.24.197.15.3.18-150200.24.197.1
SUSE:Linux Enterprise Live Patching 15 SP2kernel-livepatch-SLE15-SP2_Update_50before 1-150200.5.3.11-150200.5.3.1

Same product

linux: all records

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • 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 KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2022-48758Jun 20, 2024 · scsi: bnx2fc: Flush destroy_work queue before calling bnx2fc_interface_put()
    22Monitor
  • ← EarlierCVE-2022-48759Jun 20, 2024 · rpmsg: char: Fix race between the release of rpmsg_ctrldev and cdev
    28Monitor
  • Later →CVE-2022-48761Jun 20, 2024 · usb: xhci-plat: fix crash when suspend if remote wake enable
    21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux26fbe9772b8c459687930511444ce443011f86bfVendor (CNA)
Linux Linux546ba238535d925254e0b3f12012a5c55801e2f3Vendor (CNA)
Linux Linux5904dfd3ddaff3bf4a41c3baf0a8e8f31ed4599bVendor (CNA)
Linux Linux5f138ef224dffd15d5e5c5b095859719e0038427Vendor (CNA)
Linux Linux9340226388c66a7e090ebb00e91ed64a753b6c26Vendor (CNA)
Linux Linux9c61fce322ac2ef7fecf025285353570d60e41d6Vendor (CNA)
Linux Linuxb50f5ca60475710bbc9a3af32fbfc17b1e69c2f0Vendor (CNA)
Linux Linuxc9a18f7c5b071dce5e6939568829d40994866ab0Vendor (CNA)
Linux Linuxe3b131e30e612ff0e32de6c1cb4f69f89db29193Vendor (CNA)
debian:linux5.16.7-1 · Debian:12Package registry (OSV)
suse:kernel-default5.3.18-150200.24.197.1 · SUSE:Linux Enterprise Live Patching 15 SP2Package registry (OSV)
suse:kernel-default-base5.3.18-150200.24.197.1.150200.9.101.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSPackage registry (OSV)
suse:kernel-docs5.3.18-150200.24.197.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSPackage registry (OSV)
suse:kernel-livepatch-SLE15-SP2_Update_501-150200.5.3.1 · SUSE:Linux Enterprise Live Patching 15 SP2Package registry (OSV)
suse:kernel-obs-build5.3.18-150200.24.197.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSPackage registry (OSV)
suse:kernel-preempt5.3.18-150200.24.197.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSPackage registry (OSV)
suse:kernel-source5.3.18-150200.24.197.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSPackage registry (OSV)
suse:kernel-syms5.3.18-150200.24.197.1 · SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSSPackage 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 researchers

Finders, 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
high · data can be read
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
High
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-667 · Improper Locking

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (8 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records