Linux Kernel up to 7.1.8 ipv4 fib_nlmsg_size/fib_nexthop_info buffer size

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.2 | $5k-$25k | 0.43 |
Summary
A vulnerability has been found in Linux Kernel up to 7.1.8 and classified as critical. Affected by this issue is the function fib_nlmsg_size/fib_nexthop_info of the component ipv4. The manipulation leads to buffer size.
This vulnerability is traded as CVE-2026-74657. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability was found in Linux Kernel up to 7.1.8 and classified as critical. This issue affects the function fib_nlmsg_size/fib_nexthop_info of the component ipv4. The manipulation with an unknown input leads to a buffer size vulnerability. Using CWE to declare the problem leads to CWE-131. The product does not correctly calculate the size to be used when allocating a buffer, which could lead to a buffer overflow. Impacted is availability. The summary by CVE is:
In the Linux kernel, the following vulnerability has been resolved: ipv4: Fix fib_nlmsg_size() for RTA_VIA nexthops fib_nlmsg_size() still estimates nexthop space as if every gateway is encoded as an IPv4 RTA_GATEWAY attribute. IPv4 routes can also carry an IPv6 gateway, which fib_nexthop_info() dumps as RTA_VIA. As a result, route notifications can allocate an skb that is too small. fib_dump_info() then fails with -EMSGSIZE and rtmsg_fib() hits the WARN_ON() that marks such failures as a fib_nlmsg_size() bug. With panic_on_warn set, this becomes a kernel panic. Mirror the actual nexthop dump layout in fib_nlmsg_size(): account for IPv6 nexthop gateways dumped as RTA_VIA, for the no-header rtnexthop layout used inside RTA_MULTIPATH, and for RTA_FLOW only when it is actually present.
It is possible to read the advisory at git.kernel.org. The identification of this vulnerability is CVE-2026-74657 since 08/15/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 08/22/2026).
Upgrading to version 5.15.216, 6.1.183, 6.6.152, 6.12.104, 6.18.45 or 7.1.9 eliminates this vulnerability. Applying the patch 0f0ca602941d0a81ae9514943ca06c55159c6385/5307a53599fa762c06e475ee4a375252074fd324/7f80ad373ce4a7af5367ff273cea0f16e91387f3/4a5dfbae5179f6574695012a980476254df2d295/a59edda6eda1252340354322d8ab318b2e9052fb/9b22f13524fa0de0d963bbd3002df6c28bae3395/4ff9548d84945d2cbf9e4c207288063a200ea397 is able to eliminate this problem.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Type
Vendor
Name
Version
- 5.15.215
- 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: 7.5VulDB Meta Temp Score: 7.2
VulDB Base Score: 7.5
VulDB Temp Score: 7.2
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: Buffer sizeCWE: CWE-131 / CWE-120 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
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 5.15.216/6.1.183/6.6.152/6.12.104/6.18.45/7.1.9
Patch: 0f0ca602941d0a81ae9514943ca06c55159c6385/5307a53599fa762c06e475ee4a375252074fd324/7f80ad373ce4a7af5367ff273cea0f16e91387f3/4a5dfbae5179f6574695012a980476254df2d295/a59edda6eda1252340354322d8ab318b2e9052fb/9b22f13524fa0de0d963bbd3002df6c28bae3395/4ff9548d84945d2cbf9e4c207288063a200ea397
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-74657 (🔒)
GCVE (CVE): GCVE-0-2026-74657
GCVE (VulDB): GCVE-100-394439
Entry
Created: 08/22/2026 18:41Changes: 08/22/2026 18:41 (59)
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.