Linux: Reachable Assertion
CVE-2026-46117 is a high-severity reachable assertion vulnerability in Linux, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions 9cc0c6b1ba8cd5c55aef043e1384de0a8b4efa71, 9ef65af26b2a6738bf15812042e84b3112402d3a, db991ba50087ad99fa12a2c483aa3be19671ea73 as the first without the flaw, so updating Linux to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.14% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Linux to 9cc0c6b1ba8cd5c55aef043e1384de0a8b4efa71 or 9ef65af26b2a6738bf15812042e84b3112402d3a or db991ba50087ad99fa12a2c483aa3be19671ea73 or 159f2efabc89d3f931d38f2d35876535d4abf0a3, whichever matches your release line, or a later version.
- Update Linux Kernel to 6.12.91 or 6.18.30 or 7.0.7, whichever matches your release line, or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Linux | Linux | c15d7802a42402a87880a17eee89ff023e49ecc0 up to, but not including, 9cc0c6b1ba8cd5c55aef043e1384de0a8b4efa71; c15d7802a42402a87880a17eee89ff023e49ecc0 up to, but not including, 9ef65af26b2a6738bf15812042e84b3112402d3a; c15d7802a42402a87880a17eee89ff023e49ecc0 up to, but not including, db991ba50087ad99fa12a2c483aa3be19671ea73; c15d7802a42402a87880a17eee89ff023e49ecc0 up to, but not including, 159f2efabc89d3f931d38f2d35876535d4abf0a3; 6.8 | 9cc0c6b1ba8cd5c55aef043e1384de0a8b4efa71, 9ef65af26b2a6738bf15812042e84b3112402d3a, db991ba50087ad99fa12a2c483aa3be19671ea73, 159f2efabc89d3f931d38f2d35876535d4abf0a3 |
| Red Hat | Red Hat Enterprise Linux 10 | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 8 | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 9 | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 9.4 Update Services for SAP Solutions | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 6 | Not specified in the record | Not stated |
| Red Hat | Red Hat Enterprise Linux 7 | Not specified in the record | Not stated |
| Linux | Linux Kernel | 6.8 up to, but not including, 6.12.91; 6.13 up to, but not including, 6.18.30; 6.19 up to, but not including, 7.0.7; 7.1 | 6.12.91, 6.18.30, 7.0.7 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.8 | High | CNA |
| CVSS 3.1 | 7.0 | High | CNA |
Official description
In the Linux kernel, the following vulnerability has been resolved: RDMA/mana: Remove user triggerable WARN_ON() in mana_ib_create_qp_rss() Sashiko points out that the user can specify WQs sharing the same CQ as a part of the uAPI and this will trigger the WARN_ON() then go on to corrupt the kernel. Just reject it outright and fail the QP creation.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Reachable Assertion
The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.
How developers prevent this class of flaw
- If the assertion statement is required (e.g., for security or reliability), change the invoking code to avoid the conditions that trigger the assertion.
- Consider changing the assertion to some other less fatal error. This might not be easy to implement, since other code may be needed to handle the error.
- Make sensitive open/close operations non-reachable from directly user-controlled data (e.g. open/close resources)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Other references
- access.redhat.com/errata/RHSA-2026:27789
- access.redhat.com/errata/RHSA-2026:30129
- access.redhat.com/errata/RHSA-2026:42550
- access.redhat.com/errata/RHSA-2026:42552
- access.redhat.com/errata/RHSA-2026:65712
- access.redhat.com/errata/RHSA-2026:67720
- access.redhat.com/security/cve/CVE-2026-46117
- bugzilla.redhat.com/show_bug.cgi?id=2482576
- security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-46117.json
Recent Reachable Assertion vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 8.8 High severity
- 7.7 High severity
- 7.5 High severity
- 7.8 High severity
Spotted an error? Tell us.