LiveActive security incident?Get immediate response
CVE Record

CVE-2023-53559: ip_vti: fix potential slab-use-after-free in decode_session6

In the Linux kernel, the following vulnerability has been resolved: ip_vti: fix potential slab-use-after-free in decode_session6 When ip_vti device is set to the qdisc of the sfb type, the cb field of the sent skb may be modified during enqueuing. Then, slab-use-after-free may occur when ip_vti device sends IPv6 packets. As commit f855691975bb ("xfrm6: Fix the nexthdr offset in _decode_session6.") showed, xfrm_decode_session was originally intended only for the receive path. IP6CB(skb)->nhoff is not set during transmission. Therefore, set the cb field in the skb to 0 before sending packets.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A Linux kernel memory-safety flaw can occur when an IP VTI interface using the SFB queueing discipline transmits IPv6 traffic. A locally authenticated, low-privileged attacker may be able to trigger serious confidentiality, integrity, or availability impact, according to the supplied CVSS assessment.

Executive priority

Treat as high priority on systems matching the narrow networking configuration, especially shared or multi-user hosts. Patch through supported vendor channels after compatibility testing. Systems without ip_vti, SFB, or IPv6 transmission appear less likely to reach the vulnerable path, but should still be assessed against vendor guidance.

Technical view

SFB enqueueing may modify the socket-buffer control block. During IPv6 transmission through ip_vti, decode_session6 can then use invalid control-block state, potentially causing a slab use-after-free. The kernel fix clears the skb control block before transmission because xfrm_decode_session was intended for receive-path state.

Likely exposure

Exposure requires Linux systems with an ip_vti device configured with the SFB queueing discipline and sending IPv6 packets. The supplied data identifies affected kernel boundaries from 3.19 through 6.5, but does not provide complete distribution-specific package mappings. Confirm backports with each Linux vendor.

Exploitation context

The supplied CVSS 3.1 score is 7.8 and describes local access, low privileges, low complexity, and no user interaction. The bundle marks KEV as false and provides no cited evidence of active exploitation or a public exploit. Practical exploitability beyond triggering memory corruption is not established here.

Researcher notes

The record describes a potential slab use-after-free but assigns no CWE. Eight stable-kernel commit references indicate backports across branches. The affected-version data mixes release numbers with a commit identifier and does not clearly express every range, so exact distribution exposure and fix status require vendor confirmation.

Mitigation direction

  • Upgrade to a vendor-supported kernel containing the applicable stable fix.
  • Check distribution advisories for backported fixes and corrected package versions.
  • Where operationally acceptable, avoid combining ip_vti, SFB queueing, and IPv6 transmission until patched.
  • Prioritize exposed multi-user systems where untrusted local users can influence networking configuration or traffic.

Validation and detection

  • Inventory kernel versions and map them to distribution security advisories.
  • Identify systems with ip_vti interfaces configured to use the SFB queueing discipline.
  • Confirm whether affected interfaces transmit IPv6 traffic.
  • Verify the installed kernel includes the applicable stable commit or vendor backport.
  • Review kernel memory-safety reports or crashes, without treating their absence as proof of safety.
Prepared
Confidence
medium
Sources
10

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-53559 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

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

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.

1CVSS vectors
3Timeline events
0ADP providers
9Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2023-53559Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

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.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxf855691975bb06373a98711e4cfe2c224244b536, f855691975bb06373a98711e4cfe2c224244b536, f855691975bb06373a98711e4cfe2c224244b536, f855691975bb06373a98711e4cfe2c224244b536, f855691975bb06373a98711e4cfe2c224244b536, f855691975bb06373a98711e4cfe2c224244b536, f855691975bb06373a98711e4cfe2c224244b536, f855691975bb06373a98711e4cfe2c224244b536unaffected
LinuxLinux3.19, 0, 4.14.324, 4.19.293, 5.4.255, 5.10.192, 5.15.128, 6.1.47, 6.4.12, 6.5affected
Weakness

CWE details

No CWE listed

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