LiveActive security incident?Get immediate response
CVE Record

CVE-2024-27414: rtnetlink: fix error logic of IFLA_BRIDGE_FLAGS writing back

In the Linux kernel, the following vulnerability has been resolved: rtnetlink: fix error logic of IFLA_BRIDGE_FLAGS writing back In the commit d73ef2d69c0d ("rtnetlink: let rtnl_bridge_setlink checks IFLA_BRIDGE_MODE length"), an adjustment was made to the old loop logic in the function `rtnl_bridge_setlink` to enable the loop to also check the length of the IFLA_BRIDGE_MODE attribute. However, this adjustment removed the `break` statement and led to an error logic of the flags writing back at the end of this function. if (have_flags) memcpy(nla_data(attr), &flags, sizeof(flags)); // attr should point to IFLA_BRIDGE_FLAGS NLA !!! Before the mentioned commit, the `attr` is granted to be IFLA_BRIDGE_FLAGS. However, this is not necessarily true fow now as the updated loop will let the attr point to the last NLA, even an invalid NLA which could cause overflow writes. This patch introduces a new variable `br_flag` to save the NLA pointer that points to IFLA_BRIDGE_FLAGS and uses it to resolve the mentioned error logic.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

A Linux kernel networking bug could let a malformed bridge-related netlink attribute cause memory to be written in the wrong place. The public record does not provide a severity score, confirmed exploit use, or detailed impact beyond possible overflow writes.

Executive priority

Treat as a patch-management item with uncertain severity. It affects core Linux networking code, but public sources do not show active exploitation or a CVSS score. Prioritize normal kernel update cycles, escalating for shared infrastructure or systems exposing delegated network administration.

Technical view

In rtnl_bridge_setlink, a prior loop change could leave attr pointing at the last netlink attribute rather than IFLA_BRIDGE_FLAGS. When have_flags was true, the function wrote flags back through that stale pointer, potentially causing overflow writes. Stable fixes store the bridge flags attribute in a separate br_flag pointer.

Likely exposure

Exposure is limited to Linux systems running kernel versions identified as affected in the CVE record, including listed 5.4, 5.10, 5.15, 6.1, 6.6, 6.7, and 6.8 lines. Product-specific exposure depends on distribution backports.

Exploitation context

The source bundle does not cite active exploitation, and the CVE is not marked KEV. It describes a kernel-side error in rtnetlink bridge handling, but provides no public exploit status, attack complexity, required privileges, or confirmed real-world abuse.

Researcher notes

Useful review points are rtnl_bridge_setlink handling of IFLA_BRIDGE_FLAGS and IFLA_BRIDGE_MODE, the d73ef2d69c0d regression, and stable patches introducing br_flag. The bundle does not include exploitability analysis, prerequisites, or architecture-specific impact.

Mitigation direction

  • Upgrade to a kernel or distribution package containing the referenced stable fixes.
  • Check your Linux distribution advisory for backported fixed package versions.
  • Prioritize internet-facing or multi-tenant hosts that allow network configuration operations.
  • Track Debian LTS and vendor advisories for package-specific remediation guidance.

Validation and detection

  • Inventory running kernel versions across Linux hosts and containers' host kernels.
  • Compare versions against vendor advisories and the CVE affected-version data.
  • Verify installed kernel packages include the referenced rtnetlink bridge fix.
  • Confirm systems rebooted into the fixed kernel after patching.
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-2024-27414 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
2ADP providers
9Source links

SSVC decision data

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

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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxad46d4861ed36315d3d9e838723ba3e367ecc042, abb0172fa8dc4a4ec51aa992b7269ed65959f310, 047508edd602921ee8bb0f2aa2100aa2e9bedc75, 8dfac8071d58447e5cace4c4c6fe493ce2f615f6, d73ef2d69c0dba5f5a1cb9600045c873bab1fb7f, d73ef2d69c0dba5f5a1cb9600045c873bab1fb7f, d73ef2d69c0dba5f5a1cb9600045c873bab1fb7f, 00757f58e37b2d9a6f99e15be484712390cd2bab, 5.4.253, 5.10.190, 5.15.126, 6.1.45, 6.4.10unaffected
LinuxLinux6.5, 0, 5.4.271, 5.10.212, 5.15.151, 6.1.81, 6.6.21, 6.7.9, 6.8affected
Weakness

CWE details

No CWE listed

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