CVE-2024-27018

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2024-05-01. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2024-24280 (ENISA EUVD) · GHSA-cm9x-gp4m-whg8 (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

netfilter: br_netfilter: skip conntrack input hook for promisc packets

For historical reasons, when bridge device is in promisc mode, packets that are directed to the taps follow bridge input hook path. This patch adds a workaround to reset conntrack for these packets.

Jianbo Liu reports warning splats in their test infrastructure where cloned packets reach the br_netfilter input hook to confirm the conntrack object.

Scratch one bit from BR_INPUT_SKB_CB to annotate that this packet has reached the input hook because it is passed up to the bridge device to reach the taps.

[ 57.571874] WARNING: CPU: 1 PID: 0 at net/bridge/br_netfilter_hooks.c:616 br_nf_local_in+0x157/0x180 [br_netfilter] [ 57.572749] Modules linked in: xt_MASQUERADE nf_conntrack_netlink nfnetlink iptable_nat xt_addrtype xt_conntrack nf_nat br_netfilter rpcsec_gss_krb5 auth_rpcgss oid_registry overlay rpcrdma rdma_ucm ib_iser libiscsi scsi_transport_isc si ib_umad rdma_cm ib_ipoib iw_cm ib_cm mlx5_ib ib_uverbs ib_core mlx5ctl mlx5_core [ 57.575158] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 6.8.0+ #19 [ 57.575700] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org 04/01/2014 [ 57.576662] RIP: 0010:br_nf_local_in+0x157/0x180 [br_netfilter] [ 57.577195] Code: fe ff ff 41 bd 04 00 00 00 be 04 00 00 00 e9 4a ff ff ff be 04 00 00 00 48 89 ef e8 f3 a9 3c e1 66 83 ad b4 00 00 00 04 eb 91 <0f> 0b e9 f1 fe ff ff 0f 0b e9 df fe ff ff 48 89 df e8 b3 53 47 e1 [ 57.578722] RSP: 0018:ffff88885f845a08 EFLAGS: 00010202 [ 57.579207] RAX: 0000000000000002 RBX: ffff88812dfe8000 RCX: 0000000000000000 [ 57.579830] RDX: ffff88885f845a60 RSI: ffff8881022dc300 RDI: 0000000000000000 [ 57.580454] RBP: ffff88885f845a60 R08: 0000000000000001 R09: 0000000000000003 [ 57.581076] R10: 00000000ffff1300 R11: 0000000000000002 R12: 0000000000000000 [ 57.581695] R13: ffff8881047ffe00 R14: ffff888108dbee00 R15: ffff88814519b800 [ 57.582313] FS: 0000000000000000(0000) GS:ffff88885f840000(0000) knlGS:0000000000000000 [ 57.583040] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [ 57.583564] CR2: 000000c4206aa000 CR3: 0000000103847001 CR4: 0000000000370eb0 [ 57.584194] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 [ 57.584820] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 [ 57.585440] Call Trace: [ 57.585721] [ 57.585976] ? __warn+0x7d/0x130 [ 57.586323] ? br_nf_local_in+0x157/0x180 [br_netfilter] [ 57.586811] ? report_bug+0xf1/0x1c0 [ 57.587177] ? handle_bug+0x3f/0x70 [ 57.587539] ? exc_invalid_op+0x13/0x60 [ 57.587929] ? asm_exc_invalid_op+0x16/0x20 [ 57.588336] ? br_nf_local_in+0x157/0x180 [br_netfilter] [ 57.588825] nf_hook_slow+0x3d/0xd0 [ 57.589188] ? br_handle_vlan+0x4b/0x110 [ 57.589579] br_pass_frame_up+0xfc/0x150 [ 57.589970] ? br_port_flags_change+0x40/0x40 [ 57.590396] br_handle_frame_finish+0x346/0x5e0 [ 57.590837] ? ipt_do_table+0x32e/0x430 [ 57.591221] ? br_handle_local_finish+0x20/0x20 [ 57.591656] br_nf_hook_thresh+0x4b/0xf0 [br_netfilter] [ 57.592286] ? br_handle_local_finish+0x20/0x20 [ 57.592802] br_nf_pre_routing_finish+0x178/0x480 [br_netfilter] [ 57.593348] ? br_handle_local_finish+0x20/0x20 [ 57.593782] ? nf_nat_ipv4_pre_routing+0x25/0x60 [nf_nat] [ 57.594279] br_nf_pre_routing+0x24c/0x550 [br_netfilter] [ 57.594780] ? br_nf_hook_thresh+0xf0/0xf0 [br_netfilter] [ 57.595280] br_handle_frame+0x1f3/0x3d0 [ 57.595676] ? br_handle_local_finish+0x20/0x20 [ 57.596118] ? br_handle_frame_finish+0x5e0/0x5e0 [ 57.596566] __netif_receive_skb_core+0x25b/0xfc0 [ 57.597017] ? __napi_build_skb+0x37/0x40 [ 57.597418] __netif_receive_skb_list_core+0xfb/0x220

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.6% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.6%
EPSS %ILE
51st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

May 1, 2024

Last Modified

August 5, 2026

Advisory Details (5)

Auto-updated Aug 4, 2026
Patch available.
Web page

netfilter: br_netfilter: skip conntrack input hook for promisc packets - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/dceb683ab87ca3666a9bb5c0158528b646faedc4
Web page

netfilter: br_netfilter: skip conntrack input hook for promisc packets - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b13db0d16bc7b2a52abcf5cb71334f63faa5dbd6
Web page

netfilter: br_netfilter: skip conntrack input hook for promisc packets - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/751de2012eafa4d46d8081056761fa0e9cc8a178
Web page

netfilter: br_netfilter: skip conntrack input hook for promisc packets - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/43193174510ea4f3ce09b796e559a2fd9f148615
Web page

netfilter: br_netfilter: skip conntrack input hook for promisc packets - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3f59ac29dea0921637053908fe99268d157bbb9d

Vendor Advisories for CVE-2024-27018(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(12)

These rows come from Ubuntu and OSV. Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.27-1 ... 6.1.90-1~bpo11+1 (21 versions)
  • every version up to 6.1.90-1: fixed in 6.1.90-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.8.9-1: fixed in 6.8.9-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux—
  • every version up to 6.8.9-1: fixed in 6.8.9-1
—

Additional Vendor Advisories

(11)

Data Freshness Timeline

(refreshed 11× in last 7d / 40× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 252 rows on record for this CVE, as 99 entries (1 repeat merged).

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 152 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-22 05:35 UTCEchelonGraph re-scored
  2. 2026-11-22 05:35 UTCVendor advisory
  3. 2026-11-22 05:35 UTCGHSA enrichmentGHSA-cm9x-gp4m-whg8 · GitHub severity HIGH · GitHub CVSS 7.8
  4. 2026-11-21 16:35 UTCEPSS rescoreEPSS 0.6% · 51st percentile
  5. 2026-11-20 16:34 UTCEPSS rescoreEPSS 0.6% · 51st percentile
  6. 2026-11-19 16:30 UTCEPSS rescoreEPSS 0.6% · 51st percentile
  7. 2026-11-18 16:31 UTCEPSS rescoreEPSS 0.6% · 51st percentile
  8. 2026-11-17 16:31 UTCEPSS rescoreEPSS 0.6% · 51st percentile
  9. 2026-11-16 16:44 UTCEPSS rescoreEPSS 0.6% · 51st percentile
  10. 2026-11-16 06:56 UTCOSV refresh
  11. 2026-11-15 21:24 UTCEchelonGraph re-scored
  12. 2026-11-15 21:24 UTCVendor advisory
  13. 2026-11-15 21:24 UTCGHSA enrichmentGHSA-cm9x-gp4m-whg8 · GitHub severity HIGH · GitHub CVSS 7.8
  14. 2026-11-15 16:47 UTCEPSS rescoreEPSS 0.6% · 51st percentile
  15. 2026-11-14 16:36 UTCEPSS rescoreEPSS 0.6% · 51st percentile
  16. 2026-11-13 16:46 UTCEPSS rescoreEPSS 0.6% · 51st percentile
  17. 2026-11-12 16:31 UTCEPSS rescoreEPSS 0.6% · 51st percentile
  18. 2026-11-11 16:34 UTCEPSS rescoreEPSS 0.6% · 51st percentile
  19. 2026-11-10 16:38 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  20. 2026-11-09 16:31 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  21. 2026-11-09 11:37 UTCEchelonGraph re-scored
  22. 2026-11-09 11:37 UTCVendor advisory
  23. 2026-11-09 11:37 UTCGHSA enrichmentGHSA-cm9x-gp4m-whg8 · GitHub severity HIGH · GitHub CVSS 7.8
  24. 2026-11-08 16:35 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  25. 2026-11-07 16:35 UTCEPSS rescoreEPSS 0.6% · 50th percentile
Show 74 more
  1. 2026-11-06 16:31 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  2. 2026-11-05 16:33 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  3. 2026-11-04 16:32 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  4. 2026-11-03 16:42 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  5. 2026-11-03 03:34 UTCEchelonGraph re-scored
  6. 2026-11-03 03:34 UTCVendor advisory
  7. 2026-11-03 03:34 UTCGHSA enrichmentGHSA-cm9x-gp4m-whg8 · GitHub severity HIGH · GitHub CVSS 7.8
  8. 2026-11-02 16:40 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  9. 2026-11-01 16:31 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  10. 2026-10-31 16:30 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  11. 2026-10-30 16:31 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  12. 2026-10-29 16:30 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  13. 2026-10-28 16:29 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  14. 2026-10-27 19:30 UTCEchelonGraph re-scored
  15. 2026-10-27 19:30 UTCVendor advisory
  16. 2026-10-27 19:30 UTCGHSA enrichmentGHSA-cm9x-gp4m-whg8 · GitHub severity HIGH · GitHub CVSS 7.8
  17. 2026-10-27 16:29 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  18. 2026-10-26 16:29 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  19. 2026-10-25 17:15 UTCEchelonGraph re-scored
  20. 2026-10-25 16:30 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  21. 2026-10-24 16:30 UTCEPSS rescoreEPSS 0.6% · 50th percentile
  22. 2026-10-23 16:29 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  23. 2026-10-22 16:31 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  24. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  25. 2026-10-20 20:18 UTCEchelonGraph re-scored
  26. 2026-10-20 20:18 UTCVendor advisory
  27. 2026-10-20 20:18 UTCGHSA enrichmentGHSA-cm9x-gp4m-whg8 · GitHub severity HIGH · GitHub CVSS 7.8
  28. 2026-10-20 16:30 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  29. 2026-10-19 19:55 UTCOSV refresh
  30. 2026-10-19 16:29 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  31. 2026-10-18 16:29 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  32. 2026-10-18 07:22 UTCEchelonGraph re-scored
  33. 2026-10-17 16:30 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  34. 2026-10-16 16:36 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  35. 2026-10-15 16:29 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  36. 2026-10-14 16:30 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  37. 2026-10-13 16:30 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  38. 2026-10-12 17:59 UTCEchelonGraph re-scored
  39. 2026-10-12 16:31 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  40. 2026-10-11 21:23 UTCEchelonGraph re-scored
  41. 2026-10-11 16:17 UTCEchelonGraph re-scored
  42. 2026-10-11 13:45 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  43. 2026-10-10 19:58 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  44. 2026-10-09 20:05 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  45. 2026-10-08 17:07 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  46. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  47. 2026-10-06 15:15 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  48. 2026-10-05 17:41 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  49. 2026-10-04 23:20 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  50. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  51. 2026-10-01 19:48 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  52. 2026-09-30 17:00 UTCEchelonGraph re-scored
  53. 2026-09-30 15:01 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  54. 2026-09-29 15:17 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  55. 2026-09-28 13:49 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  56. 2026-09-27 00:42 UTCOSV refresh
  57. 2026-09-24 14:01 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  58. 2026-09-23 13:46 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  59. 2026-09-20 20:14 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  60. 2026-09-16 14:06 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  61. 2026-09-16 05:11 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  62. 2026-09-15 03:08 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  63. 2026-09-13 16:45 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  64. 2026-09-12 14:59 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  65. 2026-09-11 14:51 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  66. 2026-09-11 09:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  67. 2026-09-08 21:58 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  68. 2026-09-07 15:59 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  69. 2026-09-07 10:18 UTCOSV refresh
  70. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  71. 2026-09-05 15:26 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  72. 2026-09-04 13:58 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  73. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  74. 2026-09-02 14:10 UTCEPSS rescoreEPSS 0.6% · 47th percentile

Frequently asked(5)

What is CVE-2024-27018?
CVE-2024-27018 is a high-severity vulnerability; its CVE record was published on May 1, 2024. In the Linux kernel, the following vulnerability has been resolved: netfilter: br_netfilter: skip conntrack input hook for promisc packets For historical reasons, when bridge device is in promisc mode, packets that are directed to the taps follow bridge input hook path. This patch adds a workaround…
When was the CVE record for CVE-2024-27018 published?
The CVE record for CVE-2024-27018 was published on May 1, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 5, 2026; the record at its source may have been updated since.
Is CVE-2024-27018 actively exploited?
CVE-2024-27018 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2024-27018?
CVE-2024-27018 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2024-27018?
A fix for CVE-2024-27018 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-27018 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-27018

Explore →

Is Your Infrastructure Affected by CVE-2024-27018?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.