Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2022-50545: r6040: Fix kmemleak in probe and remove

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 2ce242e1b9ad31c1f68496b3548e407a8cb2c07d, 3d5f83a62e8235d235534b3dc6f197d8a822c269, 5944c25c67de54e0aa53623e1e1af3bf8b16ed44.

Low priority for now. Upgrade to Linux Linux 2ce242e1b9ad31c1f68496b3548e407a8cb2c07d, 3d5f83a62e8235d235534b3dc6f197d8a822c269, 5944c25c67de54e0aa53623e1e1af3bf8b16ed44 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: r6040: Fix kmemleak in probe and remove There is a memory leaks reported by kmemleak: unreferenced object 0xffff888116111000 (size 2048): comm "modprobe", pid 817, jiffies 4294759745 (age 76.502s) hex dump (first 32 bytes): 00 c4 0a 04 81 88 ff ff 08 10 11 16 81 88 ff ff ................ 08 10 11 16 81 88 ff ff 00 00 00 00 00 00 00 00 ................ backtrace: [<ffffffff815bcd82>] kmalloc_trace+0x22/0x60 [<ffffffff827e20ee>] phy_device_create+0x4e/0x90 [<ffffffff827e6072>] get_phy_device+0xd2/0x220 [<ffffffff827e7844>] mdiobus_scan+0xa4/0x2e0 [<ffffffff827e8be2>] __mdiobus_register+0x482/0x8b0 [<ffffffffa01f5d24>] r6040_init_one+0x714/0xd2c [r6040] ... The problem occurs in probe process as follows: r6040_init_one: mdiobus_register mdiobus_scan <- alloc and register phy_device, the reference count of phy_device is 3 r6040_mii_probe phy_connect <- connect to the first phy_device, so the reference count of the first phy_device is 4, others are 3 register_netdev <- fault inject succeeded, goto error handling path // error handling path err_out_mdio_unregister: mdiobus_unregister(lp->mii_bus); err_out_mdio: mdiobus_free(lp->mii_bus); <- the reference count of the first phy_device is 1, it is not released and other phy_devices are released // similarly, the remove process also has the same problem The root cause is traced to the phy_device is not disconnected when removes one r6040 device in r6040_remove_one() or on error handling path after r6040_mii probed successfully. In r6040_mii_probe(), a net ethernet device is connected to the first PHY device of mii_bus, in order to notify the connected driver when the link status changes, which is the default behavior of the PHY infrastructure to handle everything. Therefore the phy_device should be disconnected when removes one r6040 device or on error handling path. Fix it by adding phy_disconnect() when removes one r6040 device or on error handling path after r6040_mii probed successfully.

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

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

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 kernel2.6.36 and later · before 4.9.337
  • linux linux kernel4.10 and later · before 4.14.303
  • linux linux kernel4.15 and later · before 4.19.270
  • linux linux kernel4.20 and later · before 5.4.229
  • linux linux kernel5.5 and later · before 5.10.163
  • linux linux kernel5.11 and later · before 5.15.86
  • linux linux kernel5.16 and later · before 6.0.16
  • linux linux kernel6.1 and later · before 6.1.2

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.36affected
    • 3831861b4ad8fd0ad7110048eb3e155628799d2b and later · before a04707f4596952049da05756c27398c34d9a1d36affected · git
    • 3831861b4ad8fd0ad7110048eb3e155628799d2b and later · before b4448816e6a565e08236a6009c6bf48c6836cdfdaffected · git
    • 3831861b4ad8fd0ad7110048eb3e155628799d2b and later · before 2ce242e1b9ad31c1f68496b3548e407a8cb2c07daffected · git
    • 3831861b4ad8fd0ad7110048eb3e155628799d2b and later · before b0a61359026b57a287a48fbb4ba1d097023eca3eaffected · git
    • 3831861b4ad8fd0ad7110048eb3e155628799d2b and later · before 3d5f83a62e8235d235534b3dc6f197d8a822c269affected · git
    • 3831861b4ad8fd0ad7110048eb3e155628799d2b and later · before 9b5b50329e2e966831a7237dd6949e7b5362a49aaffected · git
    • 3831861b4ad8fd0ad7110048eb3e155628799d2b and later · before ad2c8f25457ca9a81e7e958148cbc26600ce3071affected · git
    • 3831861b4ad8fd0ad7110048eb3e155628799d2b and later · before 5944c25c67de54e0aa53623e1e1af3bf8b16ed44affected · git
    • 3831861b4ad8fd0ad7110048eb3e155628799d2b and later · before 7e43039a49c2da45edc1d9d7c9ede4003ab45a5faffected · git

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.4-16.1.4-1
SUSE:Linux Enterprise Live Patching 12 SP5kernel-defaultbefore 4.12.14-122.283.14.12.14-122.283.1
SUSE:Linux Enterprise Live Patching 12 SP5kgraft-patch-SLE12-SP5_Update_75before 1-8.3.11-8.3.1
SUSE:Linux Enterprise Server 12 SP5-LTSSkernel-sourcebefore 4.12.14-122.283.14.12.14-122.283.1
SUSE:Linux Enterprise Server 12 SP5-LTSSkernel-symsbefore 4.12.14-122.283.14.12.14-122.283.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-50543Oct 7, 2025 · RDMA/rxe: Fix mr->map double free
    31Monitor
  • ← EarlierCVE-2022-50544Oct 7, 2025 · usb: host: xhci: Fix potential memory leak in xhci_alloc_stream_info()
    22Monitor
  • Later →CVE-2022-50546Oct 7, 2025 · ext4: fix uninititialized value in 'ext4_evict_inode'
    31Monitor

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 Linux2ce242e1b9ad31c1f68496b3548e407a8cb2c07dVendor (CNA)
Linux Linux3d5f83a62e8235d235534b3dc6f197d8a822c269Vendor (CNA)
Linux Linux5944c25c67de54e0aa53623e1e1af3bf8b16ed44Vendor (CNA)
Linux Linux7e43039a49c2da45edc1d9d7c9ede4003ab45a5fVendor (CNA)
Linux Linux9b5b50329e2e966831a7237dd6949e7b5362a49aVendor (CNA)
Linux Linuxa04707f4596952049da05756c27398c34d9a1d36Vendor (CNA)
Linux Linuxad2c8f25457ca9a81e7e958148cbc26600ce3071Vendor (CNA)
Linux Linuxb0a61359026b57a287a48fbb4ba1d097023eca3eVendor (CNA)
Linux Linuxb4448816e6a565e08236a6009c6bf48c6836cdfdVendor (CNA)
debian:linux6.1.4-1 · Debian:12Package registry (OSV)
suse:kernel-default4.12.14-122.283.1 · SUSE:Linux Enterprise Live Patching 12 SP5Package registry (OSV)
suse:kernel-source4.12.14-122.283.1 · SUSE:Linux Enterprise Server 12 SP5-LTSSPackage registry (OSV)
suse:kernel-syms4.12.14-122.283.1 · SUSE:Linux Enterprise Server 12 SP5-LTSSPackage registry (OSV)
suse:kgraft-patch-SLE12-SP5_Update_751-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.

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-401 · Missing Release of Memory after Effective Lifetime

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 (8 more)

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

All records