Skip to content
TrackCVE
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2023-53995

net: ipv4: fix one memleak in __inet_del_ifa()

Not scoredEPSS 0.21%
Published
Updated
Reserved
Assigned by
Linux

Description

In the Linux kernel, the following vulnerability has been resolved: net: ipv4: fix one memleak in __inet_del_ifa() I got the below warning when do fuzzing test: unregister_netdevice: waiting for bond0 to become free. Usage count = 2 It can be repoduced via: ip link add bond0 type bond sysctl -w net.ipv4.conf.bond0.promote_secondaries=1 ip addr add 4.117.174.103/0 scope 0x40 dev bond0 ip addr add 192.168.100.111/255.255.255.254 scope 0 dev bond0 ip addr add 0.0.0.4/0 scope 0x40 secondary dev bond0 ip addr del 4.117.174.103/0 scope 0x40 dev bond0 ip link delete bond0 type bond In this reproduction test case, an incorrect 'last_prim' is found in __inet_del_ifa(), as a result, the secondary address(0.0.0.4/0 scope 0x40) is lost. The memory of the secondary address is leaked and the reference of in_device and net_device is leaked. Fix this problem: Look for 'last_prim' starting at location of the deleted IP and inserting the promoted IP into the location of 'last_prim'.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 5 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Deferred.

EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (7 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 0ff60a45678e67b2547256a636fd00c1667ce4fa – < 5624f26a3574500ce23929cb2c9976a0dec9920a
    • affected 0ff60a45678e67b2547256a636fd00c1667ce4fa – < 7c8ddcdab1b900bed69cad6beef477fff116289e
    • affected 0ff60a45678e67b2547256a636fd00c1667ce4fa – < 2f1e86014d0cc084886c36a2d77bc620e2d42618
    • affected 0ff60a45678e67b2547256a636fd00c1667ce4fa – < 980f8445479814509a3cd55a8eabaae1c9030a4c
    • affected 0ff60a45678e67b2547256a636fd00c1667ce4fa – < 42652af5360d30b43b06057c193739e7dfb18f42
    • affected 0ff60a45678e67b2547256a636fd00c1667ce4fa – < ac28b1ec6135649b5d78b028e47264cb3ebca5ea
  • Linux · Linux

    • affected 2.6.15
    • unaffected < 2.6.15
    • unaffected 5.4.257 – ≤ 5.4.*
    • unaffected 5.10.195 – ≤ 5.10.*
    • unaffected 5.15.132 – ≤ 5.15.*
    • unaffected 6.1.54 – ≤ 6.1.*
    • unaffected 6.5.4 – ≤ 6.5.*
    • unaffected 6.6 – ≤ *

References (6)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2023-53995 badge
[![CVE-2023-53995](https://trackcve.app/badge/CVE-2023-53995.svg)](https://trackcve.app/cve/CVE-2023-53995)

Record last updated .