Linux Kernel up to 7.1.8 IPVS ip_vs_nat_icmp out-of-bounds write

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 5.17 |
Summary
A vulnerability was found in Linux Kernel up to 6.1.182/6.6.151/6.12.103/6.18.44/7.1.8. It has been classified as very critical. The impacted element is the function ip_vs_nat_icmp of the component IPVS. The manipulation leads to out-of-bounds write.
This vulnerability is documented as CVE-2026-74724. The attack needs to be performed locally. There is not any exploit available.
Details
A vulnerability was found in Linux Kernel up to 6.1.182/6.6.151/6.12.103/6.18.44/7.1.8 and classified as very critical. This issue affects the function ip_vs_nat_icmp of the component IPVS. The manipulation with an unknown input leads to a out-of-bounds write vulnerability. Using CWE to declare the problem leads to CWE-787. The product writes data past the end, or before the beginning, of the intended buffer. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
In the Linux kernel, the following vulnerability has been resolved: ipvs: avoid out-of-bounds write in ip_vs_nat_icmp Sashiko warns that local attacker can modify the packet while it is processed by IPVS. Some places read the IP ihl field multiple times which can cause out-of-bounds access. One such place is ip_vs_nat_icmp where we can write after the validated area. Fix it by providing ciph argument just like it is done for IPv6 and use ciph->len as offset to the embedded transport header. Modify some IPv4 header checks by reading the ihl field only once.
It is possible to read the advisory at git.kernel.org. The identification of this vulnerability is CVE-2026-74724 since 08/15/2026. The exploitation is known to be easy. Attacking locally is a requirement. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/22/2026).
Upgrading to version 6.1.183, 6.6.152, 6.12.104, 6.18.45 or 7.1.9 eliminates this vulnerability. Applying the patch 3b8f79af0e98f27b932b0b416e9c52b692d31ff9/3c779b258c9c3c3567af68d4f45c2f751f35bd0e/be65fa324640c7a95e30b146159a2be5cc73f22e/a69a4b3fff5814d079beff9a1e9d369994b2ed47/243d0187ec4c3837b9b0004f18d1068e46115760/646922a0379496154e8c8faca4f8e2fd9100cacc is able to eliminate this problem.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-64411). Be aware that VulDB is the high quality source for vulnerability data.
Product
Type
Vendor
Name
Version
- 6.1.182
- 6.6.151
- 6.12.103
- 6.18.0
- 6.18.1
- 6.18.2
- 6.18.3
- 6.18.4
- 6.18.5
- 6.18.6
- 6.18.7
- 6.18.8
- 6.18.9
- 6.18.10
- 6.18.11
- 6.18.12
- 6.18.13
- 6.18.14
- 6.18.15
- 6.18.16
- 6.18.17
- 6.18.18
- 6.18.19
- 6.18.20
- 6.18.21
- 6.18.22
- 6.18.23
- 6.18.24
- 6.18.25
- 6.18.26
- 6.18.27
- 6.18.28
- 6.18.29
- 6.18.30
- 6.18.31
- 6.18.32
- 6.18.33
- 6.18.34
- 6.18.35
- 6.18.36
- 6.18.37
- 6.18.38
- 6.18.39
- 6.18.40
- 6.18.41
- 6.18.42
- 6.18.43
- 6.18.44
- 7.1.0
- 7.1.1
- 7.1.2
- 7.1.3
- 7.1.4
- 7.1.5
- 7.1.6
- 7.1.7
- 7.1.8
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.8VulDB Meta Temp Score: 8.4
VulDB Base Score: 8.8
VulDB Temp Score: 8.4
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Out-of-bounds writeCWE: CWE-787 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 6.1.183/6.6.152/6.12.104/6.18.45/7.1.9
Patch: 3b8f79af0e98f27b932b0b416e9c52b692d31ff9/3c779b258c9c3c3567af68d4f45c2f751f35bd0e/be65fa324640c7a95e30b146159a2be5cc73f22e/a69a4b3fff5814d079beff9a1e9d369994b2ed47/243d0187ec4c3837b9b0004f18d1068e46115760/646922a0379496154e8c8faca4f8e2fd9100cacc
Timeline
08/15/2026 CVE reserved08/22/2026 Advisory disclosed
08/22/2026 VulDB entry created
08/22/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2026-74724 (🔒)
GCVE (CVE): GCVE-0-2026-74724
GCVE (VulDB): GCVE-100-394511
EUVD: 🔒
Entry
Created: 08/22/2026 19:11Updated: 08/22/2026 19:20
Changes: 08/22/2026 19:11 (59), 08/22/2026 19:20 (1)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.