LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53995: net: ipv4: fix one memleak in __inet_del_ifa()

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'.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2023-53995 is a Linux kernel IPv4 bug where deleting certain addresses can lose track of a secondary address and leak kernel references. The public record describes a fuzzing-triggered leak around bonded interfaces, not remote compromise. Business urgency depends on whether affected kernels are used in systems with complex network interface automation.

Executive priority

Treat this as a kernel maintenance and reliability issue until vendor severity data says otherwise. Prioritize internet infrastructure, virtualization hosts, network appliances, and systems using Linux bonding, but the provided sources do not support emergency response for active exploitation.

Technical view

The flaw is in __inet_del_ifa(). When primary IPv4 addresses are deleted under promote_secondaries behavior, incorrect last_prim handling can lose a secondary address, leaking the secondary address memory plus in_device and net_device references. Linux stable commits adjust where last_prim is found and where the promoted IP is inserted.

Likely exposure

Exposure is Linux systems running affected kernel versions or downstream builds containing the vulnerable IPv4 address deletion logic. Risk appears most relevant where bonded interfaces and automated IPv4 address changes are used. The source bundle does not identify distributions, cloud images, containers, or appliances by name.

Exploitation context

The source describes reproduction during fuzzing and lists no CVSS score, CWE, public exploit, or CISA KEV entry. Active exploitation is not supported by the provided evidence. The described setup implies local network configuration control, but the source does not provide a formal attacker model.

Researcher notes

Evidence is limited to the CVE record and Linux stable commits. The provided affected-version data is broad and commit-oriented, so downstream exposure requires vendor mapping. Avoid overstating impact beyond kernel memory/reference leakage and potential cleanup/resource problems from IPv4 address deletion behavior.

Mitigation direction

  • Apply Linux kernel stable updates containing the referenced fixes.
  • Check your distribution vendor advisory for backported kernel packages.
  • Prioritize hosts using bonding and automated IPv4 address changes.
  • Avoid assuming container-only patching fixes the host kernel.
  • Monitor for kernel networking cleanup warnings on affected systems.

Validation and detection

  • Inventory Linux kernel versions across affected fleets.
  • Map vendor kernels to the referenced upstream stable commits.
  • Confirm patched kernels include the __inet_del_ifa() fix.
  • Review logs for netdevice unregister wait warnings.
  • Test network bonding workflows after kernel updates.
Prepared
Confidence
medium
Sources
8

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2023-53995 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
7Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux0ff60a45678e67b2547256a636fd00c1667ce4fa, 0ff60a45678e67b2547256a636fd00c1667ce4fa, 0ff60a45678e67b2547256a636fd00c1667ce4fa, 0ff60a45678e67b2547256a636fd00c1667ce4fa, 0ff60a45678e67b2547256a636fd00c1667ce4fa, 0ff60a45678e67b2547256a636fd00c1667ce4faunaffected
LinuxLinux2.6.15, 0, 5.4.257, 5.10.195, 5.15.132, 6.1.54, 6.5.4, 6.6affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.