Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2024-35839: netfilter: bridge: replace physindev with physinif in nf_bridge_info

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.22% (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 544add1f1cfb78c3dfa3e6edcf4668f6be5e730c, 7ae19ee81ca56b13c50a78de6c47d5b8fdc9d97b, 9325e3188a9cf3f69fc6f32af59844bbc5b90547; cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 Release Notes.
  • Severity is disputed: the assigning authority (CNA) scores it 7.8, NVD 5.5.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Linux Linux 544add1f1cfb78c3dfa3e6edcf4668f6be5e730c, 7ae19ee81ca56b13c50a78de6c47d5b8fdc9d97b, 9325e3188a9cf3f69fc6f32af59844bbc5b90547; cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0 Release Notes 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: netfilter: bridge: replace physindev with physinif in nf_bridge_info An skb can be added to a neigh->arp_queue while waiting for an arp reply. Where original skb's skb->dev can be different to neigh's neigh->dev. For instance in case of bridging dnated skb from one veth to another, the skb would be added to a neigh->arp_queue of the bridge. As skb->dev can be reset back to nf_bridge->physindev and used, and as there is no explicit mechanism that prevents this physindev from been freed under us (for instance neigh_flush_dev doesn't cleanup skbs from different device's neigh queue) we can crash on e.g. this stack: arp_process neigh_update skb = __skb_dequeue(&neigh->arp_queue) neigh_resolve_output(..., skb) ... br_nf_dev_xmit br_nf_pre_routing_finish_bridge_slow skb->dev = nf_bridge->physindev br_handle_frame_finish Let's use plain ifindex instead of net_device link. To peek into the original net_device we will use dev_get_by_index_rcu(). Thus either we get device and are safe to use it or we don't get it and drop skb.

MediumCVSS 5.5 · v3.1—No exploit Fix available
Published
May 17, 2024
Updated
Aug 5, 2026
EPSS
0.2% · 12th 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-35839

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.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for linux records

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

Affected versions

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

  • linux linux kernel4.2 and later · before 6.1.75
  • linux linux kernel6.2 and later · before 6.6.14
  • linux linux kernel6.7 and later · before 6.7.2

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

    • 4.2affected
    • c4e70a87d975d1f561a00abfe2d3cefa2a486c95 and later · before 7ae19ee81ca56b13c50a78de6c47d5b8fdc9d97baffected · git
    • c4e70a87d975d1f561a00abfe2d3cefa2a486c95 and later · before 9325e3188a9cf3f69fc6f32af59844bbc5b90547affected · git
    • c4e70a87d975d1f561a00abfe2d3cefa2a486c95 and later · before 544add1f1cfb78c3dfa3e6edcf4668f6be5e730caffected · git
    • c4e70a87d975d1f561a00abfe2d3cefa2a486c95 and later · before 9874808878d9eed407e3977fd11fee49de1e1d86affected · git
    • before 4.2not affected · semver
    • 6.1.75 and later · up to and including 6.1.*not affected · semver
    • 6.6.14 and later · up to and including 6.6.*not affected · semver
    • 6.7.2 and later · up to and including 6.7.*not affected · semver
    • 6.8 and laternot affected · original_commit_for_fix

Package-level exposure

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

EcosystemPackageAffected rangeFix
AlmaLinux:8bpftoolbefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernelbefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-abi-stablelistsbefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-corebefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-cross-headersbefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-debugbefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-debug-corebefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-debug-develbefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-debug-modulesbefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-debug-modules-extrabefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-develbefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-docbefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-headersbefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-modulesbefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-modules-extrabefore 4.18.0-553.27.1.el8_104.18.0-553.27.1.el8_10
AlmaLinux:8kernel-rtbefore 4.18.0-553.27.1.rt7.368.el8_104.18.0-553.27.1.rt7.368.el8_10
AlmaLinux:8kernel-rt-corebefore 4.18.0-553.27.1.rt7.368.el8_104.18.0-553.27.1.rt7.368.el8_10
AlmaLinux:8kernel-rt-debugbefore 4.18.0-553.27.1.rt7.368.el8_104.18.0-553.27.1.rt7.368.el8_10
AlmaLinux:8kernel-rt-debug-corebefore 4.18.0-553.27.1.rt7.368.el8_104.18.0-553.27.1.rt7.368.el8_10
AlmaLinux:8kernel-rt-debug-develbefore 4.18.0-553.27.1.rt7.368.el8_104.18.0-553.27.1.rt7.368.el8_10
AlmaLinux:8kernel-rt-debug-modulesbefore 4.18.0-553.27.1.rt7.368.el8_104.18.0-553.27.1.rt7.368.el8_10
AlmaLinux:8kernel-rt-debug-modules-extrabefore 4.18.0-553.27.1.rt7.368.el8_104.18.0-553.27.1.rt7.368.el8_10
AlmaLinux:8kernel-rt-develbefore 4.18.0-553.27.1.rt7.368.el8_104.18.0-553.27.1.rt7.368.el8_10
AlmaLinux:8kernel-rt-modulesbefore 4.18.0-553.27.1.rt7.368.el8_104.18.0-553.27.1.rt7.368.el8_10

+96

Same product

linux: all records

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-2023-52697May 17, 2024 · ASoC: Intel: sof_sdw_rt_sdca_jack_common: ctx->headset_codec_dev = NULL
    28Monitor
  • ← EarlierCVE-2023-52698May 17, 2024 · calipso: fix memory leak in netlbl_calipso_add_pass()
    22Monitor
  • Later →CVE-2024-35840May 17, 2024 · mptcp: use OPTION_MPTCP_MPJ_SYNACK in subflow_finish_connect()
    22Monitor

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 Linux544add1f1cfb78c3dfa3e6edcf4668f6be5e730cVendor (CNA)
Linux Linux7ae19ee81ca56b13c50a78de6c47d5b8fdc9d97bVendor (CNA)
Linux Linux9325e3188a9cf3f69fc6f32af59844bbc5b90547Vendor (CNA)
Linux Linux9874808878d9eed407e3977fd11fee49de1e1d86Vendor (CNA)
cbl2 kernel 5.15.202.1-1 on CBL-Mariner 2.0Release NotesMicrosoft (MSRC)
almalinux:bpftool7.3.0-427.33.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel5.14.0-427.33.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k5.14.0-427.33.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-core5.14.0-427.33.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug5.14.0-427.33.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-core5.14.0-427.33.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel5.14.0-427.33.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched5.14.0-427.33.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules5.14.0-427.33.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-core5.14.0-427.33.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra5.14.0-427.33.1.el9_4 · AlmaLinux:9Package registry (OSV)
almalinux:kernel-64k-devel5.14.0-427.33.1.el9_4 · AlmaLinux:9Package registry (OSV)
debian:linux6.1.76-1 · Debian:12Package registry (OSV)
opensuse:dtb-aarch646.4.0-150600.23.33.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-64kb6.4.0-150600.23.33.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-azure6.4.0-150600.8.23.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-debug6.4.0-150600.23.33.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-default6.4.0-150600.23.33.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-default-base6.4.0-150600.23.33.1.150600.12.14.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-rt6.4.0-150600.10.23.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-rt_debug6.4.0-150600.10.23.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-source-azure6.4.0-150600.8.23.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-source-rt6.4.0-150600.10.23.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-syms-azure6.4.0-150600.8.23.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:kernel-syms-rt6.4.0-150600.10.23.1 · openSUSE:Leap 15.6Package registry (OSV)

+26

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.

Credits

All researchers

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

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

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

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records