Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-49450: rxrpc: Fix listen() setting the bar too high for the prealloc rings

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.29% (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 369de57492c4f1a42563c5a3bd365822ca3bfc79, 4a3a78b7918bdd723d8c7c9786522ca969bffcc4, 5b4826657d36c218e9f08e8d3223b0edce3de88f.

Low priority for now. Upgrade to Linux Linux 369de57492c4f1a42563c5a3bd365822ca3bfc79, 4a3a78b7918bdd723d8c7c9786522ca969bffcc4, 5b4826657d36c218e9f08e8d3223b0edce3de88f 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: rxrpc: Fix listen() setting the bar too high for the prealloc rings AF_RXRPC's listen() handler lets you set the backlog up to 32 (if you bump up the sysctl), but whilst the preallocation circular buffers have 32 slots in them, one of them has to be a dead slot because we're using CIRC_CNT(). This means that listen(rxrpc_sock, 32) will cause an oops when the socket is closed because rxrpc_service_prealloc_one() allocated one too many calls and rxrpc_discard_prealloc() won't then be able to get rid of them because it'll think the ring is empty. rxrpc_release_calls_on_socket() then tries to abort them, but oopses because call->peer isn't yet set. Fix this by setting the maximum backlog to RXRPC_BACKLOG_MAX - 1 to match the ring capacity. BUG: kernel NULL pointer dereference, address: 0000000000000086 ... RIP: 0010:rxrpc_send_abort_packet+0x73/0x240 [rxrpc] Call Trace: <TASK> ? __wake_up_common_lock+0x7a/0x90 ? rxrpc_notify_socket+0x8e/0x140 [rxrpc] ? rxrpc_abort_call+0x4c/0x60 [rxrpc] rxrpc_release_calls_on_socket+0x107/0x1a0 [rxrpc] rxrpc_release+0xc9/0x1c0 [rxrpc] __sock_release+0x37/0xa0 sock_close+0x11/0x20 __fput+0x89/0x240 task_work_run+0x59/0x90 do_exit+0x319/0xaa0

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Feb 26, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 21th 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-49450

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.

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 kernel4.9 and later · before 4.9.318
  • linux linux kernel4.10 and later · before 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.121
  • linux linux kernel5.11 and later · before 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

    • 4.9affected
    • 00e907127e6f86d0f9b122d9b4347a8aa09a8b61 and later · before 61fb38cfbb1d54d3dafd0c25752f684b3cd00b32affected · git
    • 00e907127e6f86d0f9b122d9b4347a8aa09a8b61 and later · before 616f76498d5ddf26b997caf64a95cda3c8a55533affected · git
    • 00e907127e6f86d0f9b122d9b4347a8aa09a8b61 and later · before 4a3a78b7918bdd723d8c7c9786522ca969bffcc4affected · git
    • 00e907127e6f86d0f9b122d9b4347a8aa09a8b61 and later · before 91b34bf0409f43bb60453bab23c5beadd726d022affected · git
    • 00e907127e6f86d0f9b122d9b4347a8aa09a8b61 and later · before 5b4826657d36c218e9f08e8d3223b0edce3de88faffected · git
    • 00e907127e6f86d0f9b122d9b4347a8aa09a8b61 and later · before b3a9b227d5e7467b8518160ff034ea22bb9de573affected · git
    • 00e907127e6f86d0f9b122d9b4347a8aa09a8b61 and later · before 369de57492c4f1a42563c5a3bd365822ca3bfc79affected · git
    • 00e907127e6f86d0f9b122d9b4347a8aa09a8b61 and later · before e198f1930050e3115c80b67d9249f80f98a27c67affected · git
    • 00e907127e6f86d0f9b122d9b4347a8aa09a8b61 and later · before 88e22159750b0d55793302eeed8ee603f5c1a95caffected · git

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

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-49448Feb 26, 2025 · soc: bcm: Check for NULL return of devm_kzalloc()
    22Monitor
  • ← EarlierCVE-2022-49449Feb 26, 2025 · pinctrl: renesas: rzn1: Fix possible null-ptr-deref in sh_pfc_map_resources()
    22Monitor
  • Later →CVE-2022-49451Feb 26, 2025 · firmware: arm_scmi: Fix list protocols enumeration in the base protocol
    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 Linux369de57492c4f1a42563c5a3bd365822ca3bfc79Vendor (CNA)
Linux Linux4a3a78b7918bdd723d8c7c9786522ca969bffcc4Vendor (CNA)
Linux Linux5b4826657d36c218e9f08e8d3223b0edce3de88fVendor (CNA)
Linux Linux616f76498d5ddf26b997caf64a95cda3c8a55533Vendor (CNA)
Linux Linux61fb38cfbb1d54d3dafd0c25752f684b3cd00b32Vendor (CNA)
Linux Linux88e22159750b0d55793302eeed8ee603f5c1a95cVendor (CNA)
Linux Linux91b34bf0409f43bb60453bab23c5beadd726d022Vendor (CNA)
Linux Linuxb3a9b227d5e7467b8518160ff034ea22bb9de573Vendor (CNA)
Linux Linuxe198f1930050e3115c80b67d9249f80f98a27c67Vendor (CNA)
debian:linux5.18.5-1 · Debian:12Package 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.

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

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

All records