Linux Kernel up to 6.19.10 netfilter rt_mt6_check memory corruption

| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Linux Kernel up to 6.19.10. It has been classified as critical. This affects the function rt_mt6_check of the component netfilter. This manipulation causes memory corruption.
This vulnerability is handled as CVE-2026-31674. There is not any exploit available.
Upgrading the affected component is recommended.
Details
A vulnerability has been found in Linux Kernel up to 6.19.10 and classified as critical. Affected by this vulnerability is the function rt_mt6_check of the component netfilter. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
In the Linux kernel, the following vulnerability has been resolved: netfilter: ip6t_rt: reject oversized addrnr in rt_mt6_check() Reject rt match rules whose addrnr exceeds IP6T_RT_HOPS. rt_mt6() expects addrnr to stay within the bounds of rtinfo->addrs[]. Validate addrnr during rule installation so malformed rules are rejected before the match logic can use an out-of-range value.
The advisory is shared at git.kernel.org. This vulnerability is known as CVE-2026-31674 since 03/09/2026. The exploitation appears to be easy. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 04/26/2026).
The vulnerability scanner Nessus provides a plugin with the ID 310336 (Linux Distros Unpatched Vulnerability : CVE-2026-31674), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 5.10.253, 5.15.203, 6.1.168, 6.6.131, 6.12.80, 6.18.21 or 6.19.11 eliminates this vulnerability. Applying the patch 13e3e30ed3b5b67cc1db2bd58a5d09b0f07debfa/af9b7e2b765966457f4ec23be5bd34a141f89574/29ea965a1353bc8303877422f79c8211e9ba9c55/c6a503a9f4debc654e3a6a7ca1f7fce6a9953c59/ded71f5684df16fa645cca5bf4fe6b0cd8a46119/d8795fde1f78669a87c87ac29fceab2f104daa8c/a28ebf6f99de270d6338ccdc3b49f3e818f99b7b/9d3f027327c2fa265f7f85ead41294792c3296ed is able to eliminate this problem. The bugfix is ready for download at git.kernel.org. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the databases at Tenable (310336) and EUVD (EUVD-2026-25641). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
- 5.10.252
- 5.15.202
- 6.1.167
- 6.6.130
- 6.12.0
- 6.12.1
- 6.12.2
- 6.12.3
- 6.12.4
- 6.12.5
- 6.12.6
- 6.12.7
- 6.12.8
- 6.12.9
- 6.12.10
- 6.12.11
- 6.12.12
- 6.12.13
- 6.12.14
- 6.12.15
- 6.12.16
- 6.12.17
- 6.12.18
- 6.12.19
- 6.12.20
- 6.12.21
- 6.12.22
- 6.12.23
- 6.12.24
- 6.12.25
- 6.12.26
- 6.12.27
- 6.12.28
- 6.12.29
- 6.12.30
- 6.12.31
- 6.12.32
- 6.12.33
- 6.12.34
- 6.12.35
- 6.12.36
- 6.12.37
- 6.12.38
- 6.12.39
- 6.12.40
- 6.12.41
- 6.12.42
- 6.12.43
- 6.12.44
- 6.12.45
- 6.12.46
- 6.12.47
- 6.12.48
- 6.12.49
- 6.12.50
- 6.12.51
- 6.12.52
- 6.12.53
- 6.12.54
- 6.12.55
- 6.12.56
- 6.12.57
- 6.12.58
- 6.12.59
- 6.12.60
- 6.12.61
- 6.12.62
- 6.12.63
- 6.12.64
- 6.12.65
- 6.12.66
- 6.12.67
- 6.12.68
- 6.12.69
- 6.12.70
- 6.12.71
- 6.12.72
- 6.12.73
- 6.12.74
- 6.12.75
- 6.12.76
- 6.12.77
- 6.12.78
- 6.12.79
- 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.19.0
- 6.19.1
- 6.19.2
- 6.19.3
- 6.19.4
- 6.19.5
- 6.19.6
- 6.19.7
- 6.19.8
- 6.19.9
- 6.19.10
License
Website
- Vendor: https://www.kernel.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.0VulDB Meta Temp Score: 7.6
VulDB Base Score: 8.0
VulDB Temp Score: 7.6
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: Memory corruptionCWE: CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 310336
Nessus Name: Linux Distros Unpatched Vulnerability : CVE-2026-31674
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Kernel 5.10.253/5.15.203/6.1.168/6.6.131/6.12.80/6.18.21/6.19.11
Patch: 13e3e30ed3b5b67cc1db2bd58a5d09b0f07debfa/af9b7e2b765966457f4ec23be5bd34a141f89574/29ea965a1353bc8303877422f79c8211e9ba9c55/c6a503a9f4debc654e3a6a7ca1f7fce6a9953c59/ded71f5684df16fa645cca5bf4fe6b0cd8a46119/d8795fde1f78669a87c87ac29fceab2f104daa8c/a28ebf6f99de270d6338ccdc3b49f3e818f99b7b/9d3f027327c2fa265f7f85ead41294792c3296ed
Timeline
03/09/2026 CVE reserved04/25/2026 Advisory disclosed
04/25/2026 VulDB entry created
04/26/2026 VulDB entry last update
Sources
Vendor: kernel.orgAdvisory: git.kernel.org
Status: Confirmed
CVE: CVE-2026-31674 (🔒)
GCVE (CVE): GCVE-0-2026-31674
GCVE (VulDB): GCVE-100-359581
EUVD: 🔒
Entry
Created: 04/25/2026 11:33Updated: 04/26/2026 06:03
Changes: 04/25/2026 11:33 (59), 04/25/2026 13:02 (1), 04/26/2026 06:03 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.