Skip to content
Noroxi
NVD / CVE Program· CNA Linux

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

Noroxi assessment

Priority: Monitor (action score 22/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.23% (FIRST EPSS).
  • Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: Linux Linux 167d8642daa6a44b51de17f8ff0f584e1e762db7, 5.10.212, 5.15.151.
  • Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 5.5.

Low priority for now. Upgrade to Linux Linux 167d8642daa6a44b51de17f8ff0f584e1e762db7, 5.10.212, 5.15.151 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
May 17, 2024
Updated
Aug 5, 2026
EPSS
0.2% · 14th percentile
CWE
—

Report tools

JSON

Action score

22

Monitor

Low priority for now.

CVSS
22 / 40 · 5.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
5.5
CNA · Linux
7.8
2.3 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-27414

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
linuxlinux kernel
debiandebian linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • debian debian linux10.0
  • linux linux kernel5.10.190 and later · before 5.10.212
  • linux linux kernel5.15.126 and later · before 5.15.151
  • linux linux kernel6.1.45 and later · before 6.1.81
  • linux linux kernel6.4.10 and later · before 6.5
  • linux linux kernel5.4.253 and later · before 5.4.271
  • linux linux kernel6.7 and later · before 6.7.9
  • linux linux kernel6.5.1 and later · before 6.6.21
  • linux linux kernel6.5
  • linux linux kernel6.8

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 00757f58e37b2d9a6f99e15be484712390cd2bab, 6.5affected
    • ad46d4861ed36315d3d9e838723ba3e367ecc042 and later · before b9fbc44159dfc3e9a7073032752d9e03f5194a6faffected · git
    • abb0172fa8dc4a4ec51aa992b7269ed65959f310 and later · before 882a51a10ecf24ce135d573afa0872aef02c5125affected · git
    • 047508edd602921ee8bb0f2aa2100aa2e9bedc75 and later · before a1227b27fcccc99dc44f912b479e01a17e2d7d31affected · git
    • 8dfac8071d58447e5cace4c4c6fe493ce2f615f6 and later · before f2261eb994aa5757c1da046b78e3229a3ece0ad9affected · git
    • d73ef2d69c0dba5f5a1cb9600045c873bab1fb7f and later · before 167d8642daa6a44b51de17f8ff0f584e1e762db7affected · git
    • d73ef2d69c0dba5f5a1cb9600045c873bab1fb7f and later · before 831bc2728fb48a8957a824cba8c264b30dca1425affected · git
    • d73ef2d69c0dba5f5a1cb9600045c873bab1fb7f and later · before 743ad091fb46e622f1b690385bb15e3cd3daf874affected · git
    • 5.4.253 and later · before 5.4.271affected · semver
    • 5.10.190 and later · before 5.10.212affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12linuxbefore 6.1.82-16.1.82-1
Debian:13linuxbefore 6.7.9-16.7.9-1

Other highest-scoring records for the same primary product.

  • CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV
    90Now
  • CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV
    89Now
  • CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV
    85Now

Published before and after this one in the same product

  • ← EarlierCVE-2024-27412May 17, 2024 · power: supply: bq27xxx-i2c: Do not free non existing IRQ
    22Monitor
  • ← EarlierCVE-2024-27413May 17, 2024 · efi/capsule-loader: fix incorrect allocation size
    22Monitor
  • Later →CVE-2024-27415May 17, 2024 · netfilter: bridge: confirm multicast packets before passing them up the stack
    18Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux167d8642daa6a44b51de17f8ff0f584e1e762db7Vendor (CNA)
Linux Linux5.10.212Vendor (CNA)
Linux Linux5.15.151Vendor (CNA)
Linux Linux5.4.271Vendor (CNA)
Linux Linux6.1.81Vendor (CNA)
Linux Linux6.5Vendor (CNA)
Linux Linux743ad091fb46e622f1b690385bb15e3cd3daf874Vendor (CNA)
Linux Linux831bc2728fb48a8957a824cba8c264b30dca1425Vendor (CNA)
Linux Linux882a51a10ecf24ce135d573afa0872aef02c5125Vendor (CNA)
Linux Linuxa1227b27fcccc99dc44f912b479e01a17e2d7d31Vendor (CNA)
Linux Linuxb9fbc44159dfc3e9a7073032752d9e03f5194a6fVendor (CNA)
Linux Linuxf2261eb994aa5757c1da046b78e3229a3ece0ad9Vendor (CNA)
debian:linux6.1.82-1 · Debian:12Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

—

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records