Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-49322: tracing: Fix sleeping function called from invalid context on RT kernel

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.21% (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 12025abdc8539ed9d5014e2d647a3fd1bd3de5cd, 1788e6dbb61286215442b1af99e51405a6206762, 40f9fde06b25884baa0c4bd138b909a9b67218b4.

Low priority for now. Upgrade to Linux Linux 12025abdc8539ed9d5014e2d647a3fd1bd3de5cd, 1788e6dbb61286215442b1af99e51405a6206762, 40f9fde06b25884baa0c4bd138b909a9b67218b4 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: tracing: Fix sleeping function called from invalid context on RT kernel When setting bootparams="trace_event=initcall:initcall_start tp_printk=1" in the cmdline, the output_printk() was called, and the spin_lock_irqsave() was called in the atomic and irq disable interrupt context suitation. On the PREEMPT_RT kernel, these locks are replaced with sleepable rt-spinlock, so the stack calltrace will be triggered. Fix it by raw_spin_lock_irqsave when PREEMPT_RT and "trace_event=initcall:initcall_start tp_printk=1" enabled. BUG: sleeping function called from invalid context at kernel/locking/spinlock_rt.c:46 in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 1, name: swapper/0 preempt_count: 2, expected: 0 RCU nest depth: 0, expected: 0 Preemption disabled at: [<ffffffff8992303e>] try_to_wake_up+0x7e/0xba0 CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.17.1-rt17+ #19 34c5812404187a875f32bee7977f7367f9679ea7 Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.14.0-2 04/01/2014 Call Trace: <TASK> dump_stack_lvl+0x60/0x8c dump_stack+0x10/0x12 __might_resched.cold+0x11d/0x155 rt_spin_lock+0x40/0x70 trace_event_buffer_commit+0x2fa/0x4c0 ? map_vsyscall+0x93/0x93 trace_event_raw_event_initcall_start+0xbe/0x110 ? perf_trace_initcall_finish+0x210/0x210 ? probe_sched_wakeup+0x34/0x40 ? ttwu_do_wakeup+0xda/0x310 ? trace_hardirqs_on+0x35/0x170 ? map_vsyscall+0x93/0x93 do_one_initcall+0x217/0x3c0 ? trace_event_raw_event_initcall_level+0x170/0x170 ? push_cpu_stop+0x400/0x400 ? cblist_init_generic+0x241/0x290 kernel_init_freeable+0x1ac/0x347 ? _raw_spin_unlock_irq+0x65/0x80 ? rest_init+0xf0/0xf0 kernel_init+0x1e/0x150 ret_from_fork+0x22/0x30 </TASK>

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Feb 26, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 12th percentile

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

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-49322

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.14.283
  • linux linux kernel4.15 and later · before 4.19.247
  • linux linux kernel4.20 and later · before 5.4.198
  • linux linux kernel5.5 and later · before 5.10.122
  • linux linux kernel5.11 and later · before 5.15.47
  • linux linux kernel5.16 and later · before 5.17.15
  • linux linux kernel5.18 and later · before 5.18.4

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.19affected
    • 0daa2302968c13b657118d6ac92471f8fd2f3f28 and later · before be1f323fb9d9b14a505ca22d742d321769454de1affected · git
    • 0daa2302968c13b657118d6ac92471f8fd2f3f28 and later · before 40f9fde06b25884baa0c4bd138b909a9b67218b4affected · git
    • 0daa2302968c13b657118d6ac92471f8fd2f3f28 and later · before 48c6ee7d6c614f09b2c8553a95eefef6ecf196e0affected · git
    • 0daa2302968c13b657118d6ac92471f8fd2f3f28 and later · before 1788e6dbb61286215442b1af99e51405a6206762affected · git
    • 0daa2302968c13b657118d6ac92471f8fd2f3f28 and later · before 9b534640a2c6a8d88168febc82ec6d161184f2ecaffected · git
    • 0daa2302968c13b657118d6ac92471f8fd2f3f28 and later · before 43bfc4dccc416c964b53cbdc430e814f8b6f770baffected · git
    • 0daa2302968c13b657118d6ac92471f8fd2f3f28 and later · before 9abf3db8bdb63ab545034148ef2118f4d088ca59affected · git
    • 0daa2302968c13b657118d6ac92471f8fd2f3f28 and later · before 12025abdc8539ed9d5014e2d647a3fd1bd3de5cdaffected · git
    • before 3.19not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 5.18.5-15.18.5-1
Red Hat:enterprise_linux:9::appstreambpftool-debuginfobefore 0:7.3.0-427.13.1.el9_40:7.3.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-64k-debug-debuginfobefore 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-64k-debug-develbefore 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-64k-debug-devel-matchedbefore 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-64k-debuginfobefore 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-64k-develbefore 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-64k-devel-matchedbefore 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-debug-debuginfobefore 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-debug-develbefore 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-debug-devel-matchedbefore 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-debuginfobefore 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-aarch64before 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-ppc64lebefore 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-s390xbefore 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-debuginfo-common-x86_64before 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-develbefore 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-devel-matchedbefore 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-docbefore 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-rt-debug-debuginfobefore 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-rt-debuginfobefore 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-tools-debuginfobefore 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-zfcpdump-debuginfobefore 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4
Red Hat:enterprise_linux:9::appstreamkernel-zfcpdump-develbefore 0:5.14.0-427.13.1.el9_40:5.14.0-427.13.1.el9_4

+55

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-49320Feb 26, 2025 · dmaengine: zynqmp_dma: In struct zynqmp_dma_chan fix desc_size data type
    22Monitor
  • ← EarlierCVE-2022-49321Feb 26, 2025 · xprtrdma: treat all calls not a bcall when bc_serv is NULL
    22Monitor
  • Later →CVE-2022-49323Feb 26, 2025 · iommu/arm-smmu: fix possible null-ptr-deref in arm_smmu_device_probe()
    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 / packageFixed versionSource
Linux Linux12025abdc8539ed9d5014e2d647a3fd1bd3de5cdVendor (CNA)
Linux Linux1788e6dbb61286215442b1af99e51405a6206762Vendor (CNA)
Linux Linux40f9fde06b25884baa0c4bd138b909a9b67218b4Vendor (CNA)
Linux Linux43bfc4dccc416c964b53cbdc430e814f8b6f770bVendor (CNA)
Linux Linux48c6ee7d6c614f09b2c8553a95eefef6ecf196e0Vendor (CNA)
Linux Linux9abf3db8bdb63ab545034148ef2118f4d088ca59Vendor (CNA)
Linux Linux9b534640a2c6a8d88168febc82ec6d161184f2ecVendor (CNA)
Linux Linuxbe1f323fb9d9b14a505ca22d742d321769454de1Vendor (CNA)
debian:linux5.18.5-1 · Debian:12Package registry (OSV)
red hat:bpftool-debuginfo0:7.3.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-debuginfo0:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel0:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debug-devel-matched0:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-debuginfo0:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel0:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-64k-devel-matched0:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-427.13.1.el9_4 · Red Hat:enterprise_linux:9::appstreamPackage 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
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)

CWE-667 · Improper Locking

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.

Change log

  1. Fix✗ → ✓

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

References

Show all references (7 more)

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

All records