Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-49326: rtl818x: Prevent using not initialized queues

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 6ad81ad0cf5744738ce94c8e64051ddd80a1734c, 746285cf81dc19502ab238249d75f5990bd2d231, 769ec2a824deae2f1268dfda14999a4d14d0d0c5.

Low priority for now. Upgrade to Linux Linux 6ad81ad0cf5744738ce94c8e64051ddd80a1734c, 746285cf81dc19502ab238249d75f5990bd2d231, 769ec2a824deae2f1268dfda14999a4d14d0d0c5 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: rtl818x: Prevent using not initialized queues Using not existing queues can panic the kernel with rtl8180/rtl8185 cards. Ignore the skb priority for those cards, they only have one tx queue. Pierre Asselin (pa@panix.com) reported the kernel crash in the Gentoo forum: https://forums.gentoo.org/viewtopic-t-1147832-postdays-0-postorder-asc-start-25.html He also confirmed that this patch fixes the issue. In summary this happened: After updating wpa_supplicant from 2.9 to 2.10 the kernel crashed with a "divide error: 0000" when connecting to an AP. Control port tx now tries to use IEEE80211_AC_VO for the priority, which wpa_supplicants starts to use in 2.10. Since only the rtl8187se part of the driver supports QoS, the priority of the skb is set to IEEE80211_AC_BE (2) by mac80211 for rtl8180/rtl8185 cards. rtl8180 is then unconditionally reading out the priority and finally crashes on drivers/net/wireless/realtek/rtl818x/rtl8180/dev.c line 544 without this patch: idx = (ring->idx + skb_queue_len(&ring->queue)) % ring->entries "ring->entries" is zero for rtl8180/rtl8185 cards, tx_ring[2] never got initialized.

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

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

    • 3.15affected
    • fd6564fcdc0bfcd432e6e939f9538acc3905d08a and later · before b5dca2cd3f0239512da808598b4e70557eb4c2a1affected · git
    • fd6564fcdc0bfcd432e6e939f9538acc3905d08a and later · before d7e30dfc166d33470bba31a42f9bbc346e5409d5affected · git
    • fd6564fcdc0bfcd432e6e939f9538acc3905d08a and later · before 9d5e96cc1f1720019ce27b127a31695148d38bb0affected · git
    • fd6564fcdc0bfcd432e6e939f9538acc3905d08a and later · before b8ce58ab80faaea015c206382041ff3bcf5495ffaffected · git
    • fd6564fcdc0bfcd432e6e939f9538acc3905d08a and later · before 769ec2a824deae2f1268dfda14999a4d14d0d0c5affected · git
    • fd6564fcdc0bfcd432e6e939f9538acc3905d08a and later · before 6ad81ad0cf5744738ce94c8e64051ddd80a1734caffected · git
    • fd6564fcdc0bfcd432e6e939f9538acc3905d08a and later · before 9ad1981fc4de3afb7db3e8eb5a6a52d4c7d0d577affected · git
    • fd6564fcdc0bfcd432e6e939f9538acc3905d08a and later · before 98e55b0b876bde3353f4e074883d66ecb55c65a3affected · git
    • fd6564fcdc0bfcd432e6e939f9538acc3905d08a and later · before 746285cf81dc19502ab238249d75f5990bd2d231affected · 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
SUSE:Linux Enterprise Live Patching 12 SP5kernel-defaultbefore 4.12.14-122.261.14.12.14-122.261.1
SUSE:Linux Enterprise Live Patching 12 SP5kgraft-patch-SLE12-SP5_Update_69before 1-8.3.11-8.3.1
SUSE:Linux Enterprise Server 12 SP5-LTSSkernel-sourcebefore 4.12.14-122.261.14.12.14-122.261.1
SUSE:Linux Enterprise Server 12 SP5-LTSSkernel-symsbefore 4.12.14-122.261.14.12.14-122.261.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-49324Feb 26, 2025 · mips: cpc: Fix refcount leak in mips_cpc_default_phys_base
    22Monitor
  • ← EarlierCVE-2022-49325Feb 26, 2025 · tcp: add accessors to read/set tp->snd_cwnd
    22Monitor
  • Later →CVE-2022-49327Feb 26, 2025 · bcache: avoid journal no-space deadlock by reserving 1 journal bucket
    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 Linux6ad81ad0cf5744738ce94c8e64051ddd80a1734cVendor (CNA)
Linux Linux746285cf81dc19502ab238249d75f5990bd2d231Vendor (CNA)
Linux Linux769ec2a824deae2f1268dfda14999a4d14d0d0c5Vendor (CNA)
Linux Linux98e55b0b876bde3353f4e074883d66ecb55c65a3Vendor (CNA)
Linux Linux9ad1981fc4de3afb7db3e8eb5a6a52d4c7d0d577Vendor (CNA)
Linux Linux9d5e96cc1f1720019ce27b127a31695148d38bb0Vendor (CNA)
Linux Linuxb5dca2cd3f0239512da808598b4e70557eb4c2a1Vendor (CNA)
Linux Linuxb8ce58ab80faaea015c206382041ff3bcf5495ffVendor (CNA)
Linux Linuxd7e30dfc166d33470bba31a42f9bbc346e5409d5Vendor (CNA)
debian:linux5.18.5-1 · Debian:12Package registry (OSV)
suse:kernel-default4.12.14-122.261.1 · SUSE:Linux Enterprise Live Patching 12 SP5Package registry (OSV)
suse:kernel-source4.12.14-122.261.1 · SUSE:Linux Enterprise Server 12 SP5-LTSSPackage registry (OSV)
suse:kernel-syms4.12.14-122.261.1 · SUSE:Linux Enterprise Server 12 SP5-LTSSPackage registry (OSV)
suse:kgraft-patch-SLE12-SP5_Update_691-8.3.1 · SUSE:Linux Enterprise Live Patching 12 SP5Package 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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

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.

  • CVE-2024-5030299 days apartHID: core: zero-initialize the report bufferKEV
    52Plan
  • CVE-2026-52989483 days apartnvmet-tcp: propagate nvmet_tcp_build_pdu_iovec() errors to its callers
    39Monitor
  • CVE-2024-47685128 days apartnetfilter: nf_reject_ipv6: fix nf_reject_ip6_tcphdr_put()
    36Monitor
  • CVE-2026-53225484 days apartsctp: fix uninit-value in __sctp_rcv_asconf_lookup()
    36Monitor
  • CVE-2026-53170484 days apartaccel/ethosu: reject DMA commands with uninitialized length
    35Monitor
  • CVE-2026-43139434 days apartxfrm6: fix uninitialized saddr in xfrm6_get_saddr()
    34Monitor

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