Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-56644: net/ipv6: release expired exception dst cached in socket

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.71% (FIRST EPSS); higher than 53.6% of all records.
  • 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.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: Linux Linux 0b8903e6c881f72c6849d4952de742c656eb5ab9, 2.6.34, 3301ab7d5aeb0fe270f73a3d4810c9d1b6a9f045.
  • Severity is disputed: the assigning authority (CNA) scores it 7.5, NVD 5.5.

Low priority for now. Upgrade to Linux Linux 0b8903e6c881f72c6849d4952de742c656eb5ab9, 2.6.34, 3301ab7d5aeb0fe270f73a3d4810c9d1b6a9f045 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: release expired exception dst cached in socket Dst objects get leaked in ip6_negative_advice() when this function is executed for an expired IPv6 route located in the exception table. There are several conditions that must be fulfilled for the leak to occur: * an ICMPv6 packet indicating a change of the MTU for the path is received, resulting in an exception dst being created * a TCP connection that uses the exception dst for routing packets must start timing out so that TCP begins retransmissions * after the exception dst expires, the FIB6 garbage collector must not run before TCP executes ip6_negative_advice() for the expired exception dst When TCP executes ip6_negative_advice() for an exception dst that has expired and if no other socket holds a reference to the exception dst, the refcount of the exception dst is 2, which corresponds to the increment made by dst_init() and the increment made by the TCP socket for which the connection is timing out. The refcount made by the socket is never released. The refcount of the dst is decremented in sk_dst_reset() but that decrement is counteracted by a dst_hold() intentionally placed just before the sk_dst_reset() in ip6_negative_advice(). After ip6_negative_advice() has finished, there is no other object tied to the dst. The socket lost its reference stored in sk_dst_cache and the dst is no longer in the exception table. The exception dst becomes a leaked object. As a result of this dst leak, an unbalanced refcount is reported for the loopback device of a net namespace being destroyed under kernels that do not contain e5f80fcf869a ("ipv6: give an IPv6 dev to blackhole_netdev"): unregister_netdevice: waiting for lo to become free. Usage count = 2 Fix the dst leak by removing the dst_hold() in ip6_negative_advice(). The patch that introduced the dst_hold() in ip6_negative_advice() was 92f1655aa2b22 ("net: fix __dst_negative_advice() race"). But 92f1655aa2b22 merely refactored the code with regards to the dst refcount so the issue was present even before 92f1655aa2b22. The bug was introduced in 54c1a859efd9f ("ipv6: Don't drop cache route entry unless timer actually expired.") where the expired cached route is deleted and the sk_dst_cache member of the socket is set to NULL by calling dst_negative_advice() but the refcount belonging to the socket is left unbalanced. The IPv4 version - ipv4_negative_advice() - is not affected by this bug. When the TCP connection times out ipv4_negative_advice() merely resets the sk_dst_cache of the socket while decrementing the refcount of the exception dst.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
Dec 27, 2024
Updated
Oct 15, 2026
EPSS
0.7% · 53th 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.7%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.5
CNA · Linux
7.5
2.0 point gap

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

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-2024-56644

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
debiandebian linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux11.0
  • linux linux kernel2.6.34.1 and later · before 5.4.287
  • linux linux kernel5.5 and later · before 5.10.231
  • linux linux kernel5.11 and later · before 5.15.174
  • linux linux kernel5.16 and later · before 6.1.120
  • linux linux kernel2.6.33.2 and later · before 2.6.34
  • linux linux kernel6.7 and later · before 6.12.5
  • linux linux kernel6.2 and later · before 6.6.66
  • linux linux kernel2.6.34
  • linux linux kernel6.13

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

    • 9c93e9c757c7d3d96027a06b9b4c4e37ca87ded7, 2.6.34affected
    • 54c1a859efd9fd6cda05bc700315ba2519c14eba and later · before a95808252e8acc0123bacd2dff8b9af10bc145b7affected · git
    • 54c1a859efd9fd6cda05bc700315ba2519c14eba and later · before b90d061345bb8cd51fece561a800bae1c95448a6affected · git
    • 54c1a859efd9fd6cda05bc700315ba2519c14eba and later · before 0b8903e6c881f72c6849d4952de742c656eb5ab9affected · git
    • 54c1a859efd9fd6cda05bc700315ba2519c14eba and later · before 535add1e9f274502209cb997801208bbe1ae6c6faffected · git
    • 54c1a859efd9fd6cda05bc700315ba2519c14eba and later · before f43d12fd0fa8ee5b9caf8a3927e10d06431764d2affected · git
    • 54c1a859efd9fd6cda05bc700315ba2519c14eba and later · before 8b591bd522b71c42a82898290e35d32b482047e4affected · git
    • 54c1a859efd9fd6cda05bc700315ba2519c14eba and later · before 3301ab7d5aeb0fe270f73a3d4810c9d1b6a9f045affected · git
    • 2.6.33.2 and later · before 2.6.34affected · semver
    • before 2.6.34not affected · semver

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:8bpftoolbefore 4.18.0-553.69.1.el8_104.18.0-553.69.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.69.1.el8_104.18.0-553.69.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.69.1.el8_104.18.0-553.69.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.69.1.el8_104.18.0-553.69.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.69.1.el8_104.18.0-553.69.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.69.1.el8_104.18.0-553.69.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.69.1.el8_104.18.0-553.69.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.69.1.el8_104.18.0-553.69.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.69.1.el8_104.18.0-553.69.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.69.1.el8_104.18.0-553.69.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.69.1.el8_104.18.0-553.69.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.69.1.el8_104.18.0-553.69.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.69.1.el8_104.18.0-553.69.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.69.1.el8_104.18.0-553.69.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.69.1.el8_104.18.0-553.69.1.el8_10
AlmaLinux:8kernel-toolsbefore 4.18.0-553.69.1.el8_104.18.0-553.69.1.el8_10
AlmaLinux:8kernel-tools-libsbefore 4.18.0-553.69.1.el8_104.18.0-553.69.1.el8_10
AlmaLinux:8kernel-tools-libs-develbefore 4.18.0-553.69.1.el8_104.18.0-553.69.1.el8_10
AlmaLinux:8kernel-zfcpdumpbefore 4.18.0-553.69.1.el8_104.18.0-553.69.1.el8_10
AlmaLinux:8kernel-zfcpdump-corebefore 4.18.0-553.69.1.el8_104.18.0-553.69.1.el8_10
AlmaLinux:8kernel-zfcpdump-develbefore 4.18.0-553.69.1.el8_104.18.0-553.69.1.el8_10
AlmaLinux:8kernel-zfcpdump-modulesbefore 4.18.0-553.69.1.el8_104.18.0-553.69.1.el8_10
AlmaLinux:8kernel-zfcpdump-modules-extrabefore 4.18.0-553.69.1.el8_104.18.0-553.69.1.el8_10
AlmaLinux:8perfbefore 4.18.0-553.69.1.el8_104.18.0-553.69.1.el8_10

+49

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-2024-56637Dec 27, 2024 · netfilter: ipset: Hold module reference while requesting a module
    18Monitor
  • ← EarlierCVE-2024-56641Dec 27, 2024 · net/smc: initialize close_work early to avoid warning
    22Monitor
  • Later →CVE-2024-56647Dec 27, 2024 · net: Fix icmp host relookup triggering ip_rt_bug
    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 Linux0b8903e6c881f72c6849d4952de742c656eb5ab9Vendor (CNA)
Linux Linux2.6.34Vendor (CNA)
Linux Linux3301ab7d5aeb0fe270f73a3d4810c9d1b6a9f045Vendor (CNA)
Linux Linux535add1e9f274502209cb997801208bbe1ae6c6fVendor (CNA)
Linux Linux8b591bd522b71c42a82898290e35d32b482047e4Vendor (CNA)
Linux Linuxa95808252e8acc0123bacd2dff8b9af10bc145b7Vendor (CNA)
Linux Linuxb90d061345bb8cd51fece561a800bae1c95448a6Vendor (CNA)
Linux Linuxf43d12fd0fa8ee5b9caf8a3927e10d06431764d2Vendor (CNA)
almalinux:bpftool4.18.0-553.69.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel4.18.0-553.69.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-abi-stablelists4.18.0-553.69.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-core4.18.0-553.69.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-cross-headers4.18.0-553.69.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug4.18.0-553.69.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-core4.18.0-553.69.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-devel4.18.0-553.69.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules4.18.0-553.69.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-debug-modules-extra4.18.0-553.69.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-devel4.18.0-553.69.1.el8_10 · AlmaLinux:8Package registry (OSV)
almalinux:kernel-doc4.18.0-553.69.1.el8_10 · AlmaLinux:8Package registry (OSV)
debian:linux6.1.123-1 · Debian:12Package registry (OSV)
red hat:bpftool0:4.18.0-553.69.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:bpftool-debuginfo0:4.18.0-553.69.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel0:4.18.0-553.69.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-abi-stablelists0:4.18.0-553.69.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-core0:4.18.0-553.69.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug0:4.18.0-553.69.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-core0:4.18.0-553.69.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-debuginfo0:4.18.0-553.69.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)
red hat:kernel-debug-devel0:4.18.0-553.69.1.el8_10 · Red Hat:enterprise_linux:8::baseosPackage registry (OSV)

+15

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

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. SSVC exploitation— → none
  2. Fix✗ → ✓

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

References

All records