CVE-2024-27390 json
ipv6: mcast: remove one synchronize_net() barrier in ipv6_mc_down()
published 2y ago modified 3mo ago also EUVD-2024-24594
- cvss
- 5.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 13%
- public exploits
- 0
- none known
Summary
In the Linux kernel, the following vulnerability has been resolved:
ipv6: mcast: remove one synchronize_net() barrier in ipv6_mc_down()
As discussed in the past (commit 2d3916f31891 ("ipv6: fix skb drops in igmp6_event_query() and igmp6_event_report()")) I think the synchronize_net() call in ipv6_mc_down() is not needed.
Under load, synchronize_net() can last between 200 usec and 5 ms.
KASAN seems to agree as well.
Patch / fix
- Linux Linux 5.15.153, 6.1.83, 6.6.23, 6.7.11, 6.8.2, 6.9
- linux Debian 12 6.1.85-1
- linux Debian 14, Debian 13 6.7.12-1
debian advisories DEBIAN-CVE-2024-27390
- linux Ubuntu 22.04 LTS 5.15.0-112.122
- linux Ubuntu 24.04 LTS 6.8.0-35.35
- linux-aws Ubuntu 22.04 LTS 5.15.0-1063.69
- linux-aws Ubuntu 24.04 LTS 6.8.0-1009.9
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1062.70
- linux-gcp Ubuntu 24.04 LTS 6.8.0-1008.9
- linux-gke Ubuntu 22.04 LTS 5.15.0-1060.66
- linux-gke Ubuntu 24.04 LTS 6.8.0-1004.7
ubuntu advisories UBUNTU-CVE-2024-27390
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- git.kernel.org/stable/c/bfd2f3c58ad86ad33db80515e6c3503e0414e44b commit
- git.kernel.org/stable/c/9d159d6637ccce25f879d662a480541ef4ba3a50 commit
- git.kernel.org/stable/c/a03ede2282ebbd181bd6f5c38cbfcb5765afcd04 commit
- git.kernel.org/stable/c/26d4bac55750d535f1f0b8790dc26daf6089e373 commit
- git.kernel.org/stable/c/7eb06ee5921189812e6b4bfe7b0f1e878be16df7 commit
- git.kernel.org/stable/c/5da9a218340a2bc804dc4327e5804392e24a0b88 commit
- git.kernel.org/stable/c/17ef8efc00b34918b966388b2af0993811895a8c commit
Is CVE-2024-27390 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2024-27390 updated cvss 5.5
kernel: ipv6: mcast: remove one synchronize_net() barrier in ipv6_mc_down()
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 more Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 moreaffected: no fix planned “Out of support scope”
-
Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.22% chance of exploitation in the next 30 days, higher than 13% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/bfd2f3c58ad86ad33db80515e6c3503e0414e44b
-
git.kernel.org
/stable/c/9d159d6637ccce25f879d662a480541ef4ba3a50
patch
-
git.kernel.org
/stable/c/a03ede2282ebbd181bd6f5c38cbfcb5765afcd04
patch
-
git.kernel.org
/stable/c/26d4bac55750d535f1f0b8790dc26daf6089e373
patch
-
git.kernel.org
/stable/c/7eb06ee5921189812e6b4bfe7b0f1e878be16df7
patch
-
git.kernel.org
/stable/c/5da9a218340a2bc804dc4327e5804392e24a0b88
patch
-
git.kernel.org
/stable/c/17ef8efc00b34918b966388b2af0993811895a8c
patch
Sources
- CVE List CVE-2024-27390
- NVD CVE-2024-27390
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.