CVE-2022-48910: net: ipv6: ensure we call ipv6_mc_down() at most once
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 24888915364cfa410de62d8abb5df95c3b67455d, 72124e65a70b84e6303a5cd21b0ac1f27d7d61a4, 9588ac2eddc2f223ebcebf6e9f5caed84d32922b.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 24888915364cfa410de62d8abb5df95c3b67455d, 72124e65a70b84e6303a5cd21b0ac1f27d7d61a4, 9588ac2eddc2f223ebcebf6e9f5caed84d32922b 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: net: ipv6: ensure we call ipv6_mc_down() at most once There are two reasons for addrconf_notify() to be called with NETDEV_DOWN: either the network device is actually going down, or IPv6 was disabled on the interface. If either of them stays down while the other is toggled, we repeatedly call the code for NETDEV_DOWN, including ipv6_mc_down(), while never calling the corresponding ipv6_mc_up() in between. This will cause a new entry in idev->mc_tomb to be allocated for each multicast group the interface is subscribed to, which in turn leaks one struct ifmcaddr6 per nontrivial multicast group the interface is subscribed to. The following reproducer will leak at least $n objects: ip addr add ff2e::4242/32 dev eth0 autojoin sysctl -w net.ipv6.conf.eth0.disable_ipv6=1 for i in $(seq 1 $n); do ip link set up eth0; ip link set down eth0 done Joining groups with IPV6_ADD_MEMBERSHIP (unprivileged) or setting the sysctl net.ipv6.conf.eth0.forwarding to 1 (=> subscribing to ff02::2) can also be used to create a nontrivial idev->mc_list, which will the leak objects with the right up-down-sequence. Based on both sources for NETDEV_DOWN events the interface IPv6 state should be considered: - not ready if the network interface is not ready OR IPv6 is disabled for it - ready if the network interface is ready AND IPv6 is enabled for it The functions ipv6_mc_up() and ipv6_down() should only be run when this state changes. Implement this by remembering when the IPv6 state is ready, and only run ipv6_mc_down() if it actually changed from ready to not ready. The other direction (not ready -> ready) already works correctly, as: - the interface notification triggered codepath for NETDEV_UP / NETDEV_CHANGE returns early if ipv6 is disabled, and - the disable_ipv6=0 triggered codepath skips fully initializing the interface as long as addrconf_link_ready(dev) returns false - calling ipv6_mc_up() repeatedly does not leak anything
- Published
- Aug 21, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- —
Report tools
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.
Running WordPress? Scan your site free with WP Lens
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 helpAffected 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.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel3.18 and later · before 4.9.313
- linux linux kernel4.10 and later · before 4.14.278
- linux linux kernel4.15 and later · before 5.4.193
- linux linux kernel5.5 and later · before 5.10.104
- linux linux kernel5.11 and later · before 5.15.27
- linux linux kernel5.16 and later · before 5.16.13
- linux linux kernel5.17
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.18affected
- 3ce62a84d53cd3d3cc5377bbf339e9b08ddf9c36 and later · before 9a8736b2da28b24f01707f592ff059b9f90a058caffected · git
- 3ce62a84d53cd3d3cc5377bbf339e9b08ddf9c36 and later · before c71bf3229f9e9dd60ba02f5a5be02066edf57012affected · git
- 3ce62a84d53cd3d3cc5377bbf339e9b08ddf9c36 and later · before 24888915364cfa410de62d8abb5df95c3b67455daffected · git
- 3ce62a84d53cd3d3cc5377bbf339e9b08ddf9c36 and later · before 9588ac2eddc2f223ebcebf6e9f5caed84d32922baffected · git
- 3ce62a84d53cd3d3cc5377bbf339e9b08ddf9c36 and later · before f4c63b24dea9cc2043ff845dcca9aaf8109ea38aaffected · git
- 3ce62a84d53cd3d3cc5377bbf339e9b08ddf9c36 and later · before b11781515208dd31fbcd0b664078dce5dc44523faffected · git
- 3ce62a84d53cd3d3cc5377bbf339e9b08ddf9c36 and later · before 72124e65a70b84e6303a5cd21b0ac1f27d7d61a4affected · git
- 3ce62a84d53cd3d3cc5377bbf339e9b08ddf9c36 and later · before 9995b408f17ff8c7f11bc725c8aa225ba3a63b1caffected · git
- before 3.18not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 5.16.14-1 | 5.16.14-1 |
| SUSE:Linux Enterprise High Availability Extension 12 SP5 | kernel-default | before 4.12.14-122.228.1 | 4.12.14-122.228.1 |
| SUSE:Linux Enterprise Live Patching 12 SP5 | kgraft-patch-SLE12-SP5_Update_60 | before 1-8.3.1 | 1-8.3.1 |
| SUSE:Linux Enterprise Real Time 12 SP5 | kernel-rt | before 4.12.14-10.200.1 | 4.12.14-10.200.1 |
| SUSE:Linux Enterprise Real Time 12 SP5 | kernel-rt_debug | before 4.12.14-10.200.1 | 4.12.14-10.200.1 |
| SUSE:Linux Enterprise Real Time 12 SP5 | kernel-source-rt | before 4.12.14-10.200.1 | 4.12.14-10.200.1 |
| SUSE:Linux Enterprise Real Time 12 SP5 | kernel-syms-rt | before 4.12.14-10.200.1 | 4.12.14-10.200.1 |
| SUSE:Linux Enterprise Server 12 SP5 | kernel-azure | before 4.12.14-16.197.1 | 4.12.14-16.197.1 |
| SUSE:Linux Enterprise Server 12 SP5 | kernel-source | before 4.12.14-122.228.1 | 4.12.14-122.228.1 |
| SUSE:Linux Enterprise Server 12 SP5 | kernel-source-azure | before 4.12.14-16.197.1 | 4.12.14-16.197.1 |
| SUSE:Linux Enterprise Server 12 SP5 | kernel-syms | before 4.12.14-122.228.1 | 4.12.14-122.228.1 |
| SUSE:Linux Enterprise Server 12 SP5 | kernel-syms-azure | before 4.12.14-16.197.1 | 4.12.14-16.197.1 |
| SUSE:Linux Enterprise Software Development Kit 12 SP5 | kernel-docs | before 4.12.14-122.228.2 | 4.12.14-122.228.2 |
| SUSE:Linux Enterprise Software Development Kit 12 SP5 | kernel-obs-build | before 4.12.14-122.228.2 | 4.12.14-122.228.2 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- 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 KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2022-48908Aug 21, 2024 · net: arcnet: com20020: Fix null-ptr-deref in com20020pci_probe()22Monitor
- ← EarlierCVE-2022-48909Aug 21, 2024 · net/smc: fix connection leak22Monitor
- Later →CVE-2022-48911Aug 21, 2024 · netfilter: nf_queue: fix possible use-after-free22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 24888915364cfa410de62d8abb5df95c3b67455d | Vendor (CNA) |
| Linux Linux | 72124e65a70b84e6303a5cd21b0ac1f27d7d61a4 | Vendor (CNA) |
| Linux Linux | 9588ac2eddc2f223ebcebf6e9f5caed84d32922b | Vendor (CNA) |
| Linux Linux | 9995b408f17ff8c7f11bc725c8aa225ba3a63b1c | Vendor (CNA) |
| Linux Linux | 9a8736b2da28b24f01707f592ff059b9f90a058c | Vendor (CNA) |
| Linux Linux | b11781515208dd31fbcd0b664078dce5dc44523f | Vendor (CNA) |
| Linux Linux | c71bf3229f9e9dd60ba02f5a5be02066edf57012 | Vendor (CNA) |
| Linux Linux | f4c63b24dea9cc2043ff845dcca9aaf8109ea38a | Vendor (CNA) |
| debian:linux | 5.16.14-1 · Debian:12 | Package registry (OSV) |
| suse:kernel-azure | 4.12.14-16.197.1 · SUSE:Linux Enterprise Server 12 SP5 | Package registry (OSV) |
| suse:kernel-default | 4.12.14-122.228.1 · SUSE:Linux Enterprise High Availability Extension 12 SP5 | Package registry (OSV) |
| suse:kernel-docs | 4.12.14-122.228.2 · SUSE:Linux Enterprise Software Development Kit 12 SP5 | Package registry (OSV) |
| suse:kernel-obs-build | 4.12.14-122.228.2 · SUSE:Linux Enterprise Software Development Kit 12 SP5 | Package registry (OSV) |
| suse:kernel-rt | 4.12.14-10.200.1 · SUSE:Linux Enterprise Real Time 12 SP5 | Package registry (OSV) |
| suse:kernel-rt_debug | 4.12.14-10.200.1 · SUSE:Linux Enterprise Real Time 12 SP5 | Package registry (OSV) |
| suse:kernel-source | 4.12.14-122.228.1 · SUSE:Linux Enterprise Server 12 SP5 | Package registry (OSV) |
| suse:kernel-source-azure | 4.12.14-16.197.1 · SUSE:Linux Enterprise Server 12 SP5 | Package registry (OSV) |
| suse:kernel-source-rt | 4.12.14-10.200.1 · SUSE:Linux Enterprise Real Time 12 SP5 | Package registry (OSV) |
| suse:kernel-syms | 4.12.14-122.228.1 · SUSE:Linux Enterprise Server 12 SP5 | Package registry (OSV) |
| suse:kernel-syms-rt | 4.12.14-10.200.1 · SUSE:Linux Enterprise Real Time 12 SP5 | Package registry (OSV) |
| suse:kgraft-patch-SLE12-SP5_Update_60 | 1-8.3.1 · SUSE:Linux Enterprise Live Patching 12 SP5 | Package 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.
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.
Credits
All researchersFinders, 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).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-24-1311 · Aug 22, 2024(Linux Kernel Güvenlik Bildirimi)
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
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/72124e65a70b84e6303a5cd21b0ac1f27d7d61a4
- git.kernel.org/stable/c/9588ac2eddc2f223ebcebf6e9f5caed84d32922b
- git.kernel.org/stable/c/9995b408f17ff8c7f11bc725c8aa225ba3a63b1c
- git.kernel.org/stable/c/9a8736b2da28b24f01707f592ff059b9f90a058c
- git.kernel.org/stable/c/b11781515208dd31fbcd0b664078dce5dc44523f
- git.kernel.org/stable/c/c71bf3229f9e9dd60ba02f5a5be02066edf57012
- git.kernel.org/stable/c/f4c63b24dea9cc2043ff845dcca9aaf8109ea38a
Vendor advisories and official records. Exploit/PoC links are deliberately left out.