Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-49440: powerpc/rtas: Keep MSR[RI] set when calling RTAS

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.26% (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 5ca40fcf0da0ce2b5bc44e7d8b036535955f2e3d, 5f4367448f6817c8a0e94dc9736ed84fa8eee4a3, b6b1c3ce06ca438eb24e0f45bf0e63ecad0369f5.

Low priority for now. Upgrade to Linux Linux 5ca40fcf0da0ce2b5bc44e7d8b036535955f2e3d, 5f4367448f6817c8a0e94dc9736ed84fa8eee4a3, b6b1c3ce06ca438eb24e0f45bf0e63ecad0369f5 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: powerpc/rtas: Keep MSR[RI] set when calling RTAS RTAS runs in real mode (MSR[DR] and MSR[IR] unset) and in 32-bit big endian mode (MSR[SF,LE] unset). The change in MSR is done in enter_rtas() in a relatively complex way, since the MSR value could be hardcoded. Furthermore, a panic has been reported when hitting the watchdog interrupt while running in RTAS, this leads to the following stack trace: watchdog: CPU 24 Hard LOCKUP watchdog: CPU 24 TB:997512652051031, last heartbeat TB:997504470175378 (15980ms ago) ... Supported: No, Unreleased kernel CPU: 24 PID: 87504 Comm: drmgr Kdump: loaded Tainted: G E X 5.14.21-150400.71.1.bz196362_2-default #1 SLE15-SP4 (unreleased) 0d821077ef4faa8dfaf370efb5fdca1fa35f4e2c NIP: 000000001fb41050 LR: 000000001fb4104c CTR: 0000000000000000 REGS: c00000000fc33d60 TRAP: 0100 Tainted: G E X (5.14.21-150400.71.1.bz196362_2-default) MSR: 8000000002981000 <SF,VEC,VSX,ME> CR: 48800002 XER: 20040020 CFAR: 000000000000011c IRQMASK: 1 GPR00: 0000000000000003 ffffffffffffffff 0000000000000001 00000000000050dc GPR04: 000000001ffb6100 0000000000000020 0000000000000001 000000001fb09010 GPR08: 0000000020000000 0000000000000000 0000000000000000 0000000000000000 GPR12: 80040000072a40a8 c00000000ff8b680 0000000000000007 0000000000000034 GPR16: 000000001fbf6e94 000000001fbf6d84 000000001fbd1db0 000000001fb3f008 GPR20: 000000001fb41018 ffffffffffffffff 000000000000017f fffffffffffff68f GPR24: 000000001fb18fe8 000000001fb3e000 000000001fb1adc0 000000001fb1cf40 GPR28: 000000001fb26000 000000001fb460f0 000000001fb17f18 000000001fb17000 NIP [000000001fb41050] 0x1fb41050 LR [000000001fb4104c] 0x1fb4104c Call Trace: Instruction dump: XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX Oops: Unrecoverable System Reset, sig: 6 [#1] LE PAGE_SIZE=64K MMU=Hash SMP NR_CPUS=2048 NUMA pSeries ... Supported: No, Unreleased kernel CPU: 24 PID: 87504 Comm: drmgr Kdump: loaded Tainted: G E X 5.14.21-150400.71.1.bz196362_2-default #1 SLE15-SP4 (unreleased) 0d821077ef4faa8dfaf370efb5fdca1fa35f4e2c NIP: 000000001fb41050 LR: 000000001fb4104c CTR: 0000000000000000 REGS: c00000000fc33d60 TRAP: 0100 Tainted: G E X (5.14.21-150400.71.1.bz196362_2-default) MSR: 8000000002981000 <SF,VEC,VSX,ME> CR: 48800002 XER: 20040020 CFAR: 000000000000011c IRQMASK: 1 GPR00: 0000000000000003 ffffffffffffffff 0000000000000001 00000000000050dc GPR04: 000000001ffb6100 0000000000000020 0000000000000001 000000001fb09010 GPR08: 0000000020000000 0000000000000000 0000000000000000 0000000000000000 GPR12: 80040000072a40a8 c00000000ff8b680 0000000000000007 0000000000000034 GPR16: 000000001fbf6e94 000000001fbf6d84 000000001fbd1db0 000000001fb3f008 GPR20: 000000001fb41018 ffffffffffffffff 000000000000017f fffffffffffff68f GPR24: 000000001fb18fe8 000000001fb3e000 000000001fb1adc0 000000001fb1cf40 GPR28: 000000001fb26000 000000001fb460f0 000000001fb17f18 000000001fb17000 NIP [000000001fb41050] 0x1fb41050 LR [000000001fb4104c] 0x1fb4104c Call Trace: Instruction dump: XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX XXXXXXXX ---[ end trace 3ddec07f638c34a2 ]--- This happens because MSR[RI] is unset when entering RTAS but there is no valid reason to not set it here. RTAS is expected to be called with MSR[RI] as specified in PAPR+ section "7.2.1 Machine State": R1–7.2.1–9. If called with MSR[RI] equal to 1, then RTAS must protect its own critical regions from recursion by setting the MSR[RI] bit to 0 when in the critical regions. Fixing this by reviewing the way MSR is compute before calling RTAS. Now a hardcoded value meaning real ---truncated---

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

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%

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

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 5.15.46
  • linux linux kernel5.16 and later · before 5.17.14
  • linux linux kernel5.18 and later · before 5.18.3

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.34affected
    • 44c9f3cc1a07503b653b571eac5792436da39a30 and later · before 5ca40fcf0da0ce2b5bc44e7d8b036535955f2e3daffected · git
    • 44c9f3cc1a07503b653b571eac5792436da39a30 and later · before 5f4367448f6817c8a0e94dc9736ed84fa8eee4a3affected · git
    • 44c9f3cc1a07503b653b571eac5792436da39a30 and later · before c9c41f0273826a13ac93124e66a4ff45df281ba0affected · git
    • 44c9f3cc1a07503b653b571eac5792436da39a30 and later · before b6b1c3ce06ca438eb24e0f45bf0e63ecad0369f5affected · git
    • before 2.6.34not affected · semver
    • 5.15.46 and later · up to and including 5.15.*not affected · semver
    • 5.17.14 and later · up to and including 5.17.*not affected · semver
    • 5.18.3 and later · up to and including 5.18.*not affected · semver
    • 5.19 and laternot affected · original_commit_for_fix

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:rhel_eus:9.0::appstreambpftool-debuginfobefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::appstreamkernel-debug-debuginfobefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::appstreamkernel-debug-develbefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::appstreamkernel-debug-devel-matchedbefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::appstreamkernel-debuginfobefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::appstreamkernel-debuginfo-common-aarch64before 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::appstreamkernel-debuginfo-common-ppc64lebefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::appstreamkernel-debuginfo-common-s390xbefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::appstreamkernel-debuginfo-common-x86_64before 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::appstreamkernel-develbefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::appstreamkernel-devel-matchedbefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::appstreamkernel-docbefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::appstreamkernel-tools-debuginfobefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::appstreamkernel-zfcpdump-debuginfobefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::appstreamkernel-zfcpdump-develbefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::appstreamkernel-zfcpdump-devel-matchedbefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::appstreamperfbefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::appstreamperf-debuginfobefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::appstreampython3-perf-debuginfobefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::baseosbpftoolbefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::baseoskernelbefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::baseoskernel-abi-stablelistsbefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0
Red Hat:rhel_eus:9.0::baseoskernel-corebefore 0:5.14.0-70.43.1.el9_00:5.14.0-70.43.1.el9_0

+14

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-49438Feb 26, 2025 · Input: sparcspkr - fix refcount leak in bbc_beep_probe
    22Monitor
  • ← EarlierCVE-2022-49439Feb 26, 2025 · powerpc/fsl_rio: Fix refcount leak in fsl_rio_setup
    22Monitor
  • Later →CVE-2022-49441Feb 26, 2025 · tty: fix deadlock caused by calling printk() under tty_port->lock
    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 Linux5ca40fcf0da0ce2b5bc44e7d8b036535955f2e3dVendor (CNA)
Linux Linux5f4367448f6817c8a0e94dc9736ed84fa8eee4a3Vendor (CNA)
Linux Linuxb6b1c3ce06ca438eb24e0f45bf0e63ecad0369f5Vendor (CNA)
Linux Linuxc9c41f0273826a13ac93124e66a4ff45df281ba0Vendor (CNA)
debian:linux5.18.5-1 · Debian:12Package registry (OSV)
red hat:bpftool-debuginfo0:5.14.0-70.43.1.el9_0 · Red Hat:rhel_eus:9.0::appstreamPackage registry (OSV)
red hat:kernel-debug-debuginfo0:5.14.0-70.43.1.el9_0 · Red Hat:rhel_eus:9.0::appstreamPackage registry (OSV)
red hat:kernel-debug-devel0:5.14.0-70.43.1.el9_0 · Red Hat:rhel_eus:9.0::appstreamPackage registry (OSV)
red hat:kernel-debug-devel-matched0:5.14.0-70.43.1.el9_0 · Red Hat:rhel_eus:9.0::appstreamPackage registry (OSV)
red hat:kernel-debuginfo0:5.14.0-70.43.1.el9_0 · Red Hat:rhel_eus:9.0::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-aarch640:5.14.0-70.43.1.el9_0 · Red Hat:rhel_eus:9.0::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-ppc64le0:5.14.0-70.43.1.el9_0 · Red Hat:rhel_eus:9.0::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-s390x0:5.14.0-70.43.1.el9_0 · Red Hat:rhel_eus:9.0::appstreamPackage registry (OSV)
red hat:kernel-debuginfo-common-x86_640:5.14.0-70.43.1.el9_0 · Red Hat:rhel_eus:9.0::appstreamPackage registry (OSV)
red hat:kernel-devel0:5.14.0-70.43.1.el9_0 · Red Hat:rhel_eus:9.0::appstreamPackage registry (OSV)
red hat:kernel-devel-matched0:5.14.0-70.43.1.el9_0 · Red Hat:rhel_eus:9.0::appstreamPackage registry (OSV)
red hat:kernel-doc0:5.14.0-70.43.1.el9_0 · Red Hat:rhel_eus:9.0::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)

—

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

  1. Fix✗ → ✓

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

References

Show all references (3 more)

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

All records