LiveActive security incident?Get immediate response
CVE Record

CVE-2024-42284: tipc: Return non-zero value from tipc_udp_addr2str() on error

In the Linux kernel, the following vulnerability has been resolved: tipc: Return non-zero value from tipc_udp_addr2str() on error tipc_udp_addr2str() should return non-zero value if the UDP media address is invalid. Otherwise, a buffer overflow access can occur in tipc_media_addr_printf(). Fix this by returning 1 on an invalid UDP media address.

CriticalCVSS 9.1Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A Linux kernel flaw in TIPC’s UDP address handling can cause out-of-bounds buffer access when an invalid media address is formatted. The supplied CVSS rates remote, unauthenticated impact as critical, with potential confidentiality loss and service disruption. Actual exposure depends on whether affected kernel code and TIPC-over-UDP functionality are present and reachable.

Executive priority

Prioritize prompt assessment and patching because the supplied severity is critical and the potential path requires no privileges or user interaction. Start with clustered, telecommunications, or other systems known to use TIPC over UDP. Urgency may be lower for systems where TIPC is absent or unused, but confirm that condition rather than assuming it.

Technical view

tipc_udp_addr2str() incorrectly reported success for an invalid UDP media address. Its caller, tipc_media_addr_printf(), could then perform a buffer overflow access. Linux stable commits change the function to return a non-zero error value. The supplied vector is CVSS 3.1 9.1: network-accessible, low complexity, no privileges or interaction, with high confidentiality and availability impact.

Likely exposure

Potentially exposed systems run an affected Linux kernel and use reachable TIPC UDP media. Systems without TIPC-over-UDP use may have substantially reduced practical exposure, but the bundle does not establish every distribution’s configuration or backport status. Kernel version strings alone may be insufficient because vendors commonly backport fixes.

Exploitation context

The bundle does not provide evidence of active exploitation, and the CVE is not identified as being in KEV. The CVSS assessment indicates a theoretically remote, unauthenticated attack path, but no cited source establishes public exploitation, exploit maturity, or observed attacks. Treat exposure as configuration-dependent rather than assuming every affected kernel is remotely reachable.

Researcher notes

The defect is an error-propagation failure: an invalid UDP media address receives a success return, allowing unsafe formatting downstream. The stable fix returns 1 for invalid input. The supplied affected-version data is ambiguous and repetitive, so determine branch applicability through vendor advisories and commit inclusion. No CWE, proof of exploitation, or complete distribution matrix is supplied.

Mitigation direction

  • Install a vendor-supported kernel containing the applicable stable fix, following distribution guidance.
  • Prioritize systems where TIPC over UDP is enabled or network-reachable.
  • Apply relevant Debian security updates where the cited Debian advisories cover deployed releases.
  • Use vendor guidance for interim controls when immediate kernel replacement is not possible.
  • Reboot into the updated kernel when required by the operating-system vendor.

Validation and detection

  • Inventory running kernel builds and determine whether TIPC UDP media is enabled or used.
  • Check vendor advisories for backported fixes instead of relying only on version strings.
  • Confirm the installed kernel contains the applicable Linux stable fix commit.
  • After remediation, verify systems are running the updated kernel rather than an older installed build.
  • Review network exposure around systems using TIPC over UDP.
Prepared
Confidence
medium
Sources
6

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-2024-42284 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
Critical
CVSS
9.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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
2ADP providers
11Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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
9.1CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H3.95.2Linux

Vulnerability scoring details

Base CVSS 3.1 score

9.1Critical
CVSS 3.1 vector shape for CVE-2024-42284Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
CVECVE Program Container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxd0f91938bede204a343473792529e0db7d599836, d0f91938bede204a343473792529e0db7d599836, d0f91938bede204a343473792529e0db7d599836, d0f91938bede204a343473792529e0db7d599836, d0f91938bede204a343473792529e0db7d599836, d0f91938bede204a343473792529e0db7d599836, d0f91938bede204a343473792529e0db7d599836, d0f91938bede204a343473792529e0db7d599836unaffected
LinuxLinux4.1, 0, 4.19.320, 5.4.282, 5.10.224, 5.15.165, 6.1.103, 6.6.44, 6.10.3, 6.11affected
Weakness

CWE details

No CWE listed

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