Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-47678icmp: change the order of rate limits

Description

In the Linux kernel, the following vulnerability has been resolved: icmp: change the order of rate limits ICMP messages are ratelimited : After the blamed commits, the two rate limiters are applied in this order: 1) host wide ratelimit (icmp_global_allow()) 2) Per destination ratelimit (inetpeer based) In order to avoid side-channels attacks, we need to apply the per destination check first. This patch makes the following change : 1) icmp_global_allow() checks if the host wide limit is reached. But credits are not yet consumed. This is deferred to 3) 2) The per destination limit is checked/updated. This might add a new node in inetpeer tree. 3) icmp_global_consume() consumes tokens if prior operations succeeded. This means that host wide ratelimit is still effective in keeping inetpeer tree small even under DDOS. As a bonus, I removed icmp_global.lock as the fast path can use a lock-free operation.

Timeline

  1. ID reserved

    By Linux

  2. · 21 days later

    Published

  3. · 22 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-47678, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1Critical9.4CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS (exploitation in 30 days)
0.61% · top 50% of all CVEs (17 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Critical 9.4.

Affected products

  • Linux · Linux

    • affected 4cdf507d54525842dfd9f6313fdafba039084046 – < 997ba8889611891f91e8ad83583466aeab6239a3
    • affected 4cdf507d54525842dfd9f6313fdafba039084046 – < 662ec52260cc07b9ae53ecd3925183c29d34288b
    • affected 4cdf507d54525842dfd9f6313fdafba039084046 – < a7722921adb046e3836eb84372241f32584bdb07
    • affected 4cdf507d54525842dfd9f6313fdafba039084046 – < 483397b4ba280813e4a9c161a0a85172ddb43d19
    • affected 4cdf507d54525842dfd9f6313fdafba039084046 – < 8c2bd38b95f75f3d2a08c93e35303e26d480d24e
  • Linux · Linux

    • affected 3.18
    • unaffected < 3.18
    • unaffected 6.1.113 – ≤ 6.1.*
    • unaffected 6.6.54 – ≤ 6.6.*
    • unaffected 6.10.13 – ≤ 6.10.*
    • unaffected 6.11.2 – ≤ 6.11.*
    • unaffected 6.12 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-47678 badge
[![CVE-2024-47678](https://cveledger.app/badge/CVE-2024-47678.svg)](https://cveledger.app/cve/CVE-2024-47678)

Record last updated .