critical CVSS 9.8 EPSS 0.62%

CVE-2026-98490·Kernel vulnerability

In the Linux kernel, the following vulnerability has been resolved: net: openvswitch: conntrack: fix helper UAF due to extensions realloc While calling the helpers, a raw pointer to the extensions area is wired into expectations list: -> nf_ct_helper() -> helper->help() -> nf_ct_expect_related_report() -> nf_ct_expect_insert() -> hlist_add_head_rcu(&exp->lnode, &master_help->expectations) In case the connection is not confirmed yet, more extensions can be added afterwards with *_ext_add() calls reallocating the extension space and leaving the now invalid pointer in the expectations list that is later accessed while removing the expectation. Make sure that helpers are called at the end after all the other extensions are already added. Note that the helper rejection now leaves the mark and labels set, but that's not different from how the NAT was handled before or how the mark and the labels were handled on confirmation failure. And there are no atomicity guarantees provided by the API anyway.

Severity
critical
Software
Kernel
Fixed in
5.10.273, 5.15.224, 6.1.191, 6.6.160, 6.12.112, 6.18.55, 7.2.9, 7.3
Published

How likely is exploitation

FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.62% — higher than 49% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.

Read the two together. CVE-2026-98490 scores 9.8 on CVSS, so a successful attack would be serious — but at 0.62%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.

How to fix this CVE

Update your Linux kernel to a patched stable release to mitigate this use-after-free vulnerability in the netfilter conntrack helper subsystem. Users should upgrade to kernel 6.6.160, 6.12.112, 6.18.55, 7.2.9 or later depending on their current kernel branch, or install a patched kernel package provided by their Linux distribution.

sudo dnf update kernel kernel-devel

Defensia detects this vulnerability

How to check if you are affected

  1. Check kernel version: uname -r
  2. Determine if OpenVSwitch with conntrack is in use: lsmod | grep openvswitch && lsmod | grep nf_conntrack
  3. Review kernel logs for memory corruption or UAF errors: dmesg | grep -i 'use.*after.*free\|segfault\|kernel.*panic' | tail -20
  4. Verify the fix by comparing your kernel version against the fixed releases (6.6.160+, 6.12.112+, 6.18.55+, 7.2.9+): uname -r | awk -F'.' '{print $1"."$2"."$3}'

FAQ

What is CVE-2026-98490?

This is a use-after-free vulnerability in the Linux kernel's OpenVSwitch conntrack helper implementation where extension reallocation leaves dangling pointers in the expectations list, potentially leading to memory corruption or code execution when expectations are processed.

Is CVE-2026-98490 being actively exploited?

No, this vulnerability is not listed on the CISA Known Exploited Vulnerabilities catalog and no public exploits are currently available.

What versions of Kernel are affected by CVE-2026-98490?

All kernel versions prior to the stable fixes are affected: upgrade from 6.6.x to 6.6.160+, 6.12.x to 6.12.112+, 6.18.x to 6.18.55+, or 7.2.x to 7.2.9+.

How do I check if my server is vulnerable to CVE-2026-98490?

Run 'uname -r' to obtain your kernel version, then compare against the patched versions listed above. If your version is older than the respective fixed release for your branch, you are vulnerable.

Does Defensia detect CVE-2026-98490?

Yes — Defensia's CVE advisory scanner compares installed kernel package versions against the NVD database. If the Linux kernel is installed on a monitored server running a vulnerable version, CVE-2026-98490 will appear in your dashboard with remediation steps and distro-specific patch commands.

Related Kernel CVEs

CVE-2026-63795CVSS 10In the Linux kernel, the following vulnerability has been resolved: 9p: avoid putting oldfid in p9_client_walk() error path When p9_client_walk() is called with clone set to false, fid aliases oldfid. If the walk subsequently fails after the request has been sent, the error path jumps to clunk_fid, which currently calls p9_fid_put(fid) unconditionally. This drops a reference to oldfid even though ownership of oldfid remains with the caller. If this is the last reference, oldfid can be clunked and destroyed while the caller still expects it to be valid. A later use or put of oldfid can then trigger a use-after-free or refcount underflow. Fix this by only putting fid in the clunk_fid error path when it does not alias oldfid, matching the existing guard in the error path below. This can be triggered when a multi-component walk is split into multiple p9_client_walk() calls and a later non-cloning walk fails. A reproducer and refcount warning logs are available on request.
CVE-2026-64136CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: smb: client: protect tc_count increment in smb2_find_smb_sess_tcon_unlocked() Commit 96c4af418586 ("cifs: Fix locking usage for tcon fields") refactored cifs code to change cifs_tcp_ses_lock for tc_lock around tc_count changes. There was missing lock around tc_count increment inside smb2_find_smb_sess_tcon_unlocked().
CVE-2026-98323CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: RDMA/siw: Bound fragmented header copies by the remaining length siw_get_hdr() can receive an extended DDP/RDMAP header across more than one TCP callback. The first callback may receive most of the header, while the next one still limits the copy to hdrlen - MIN_DDP_HDR instead of the number of missing bytes. This makes the destination move past the end of the header and overwrite the receive state, including fpdu_part_rcvd. A later callback can then use a negative fpdu_part_rcvd value as a copy offset, which creates an OOB write. Use the number of header bytes already received when calculating the next copy length.
CVE-2026-98365CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: RDMA/rxe: Fix integer overflow in mr_check_range() leading to OOB access mr_check_range() validates that [iova, iova+length) falls within the registered MR range using wraparound-prone arithmetic: if (iova < mr->ibmr.iova || iova + length > mr->ibmr.iova + mr->ibmr.length) A remote peer can craft an RDMA-Write/Read RETH so that iova + length wraps to 0 (e.g. iova=0xfffffffffffffff8, length=8), bypassing the check. rxe_mr_iova_to_index() then computes a huge index (int idx, only guarded by WARN_ON) and rxe_mr_copy_xarray() dereferences mr->page_info[huge], causing an out-of-bounds read/write and a kernel oops that is triggerable by an unauthenticated remote peer. Rewrite the check in overflow-safe form; the first two clauses guarantee that the subsequent subtractions do not underflow: if (iova < mr->ibmr.iova || length > mr->ibmr.length || iova - mr->ibmr.iova > mr->ibmr.length - length) With the fix, mr_check_range() returns -EINVAL for the crafted iova and the responder reports REMOTE_ACCESS_ERROR instead of triggering the OOB.
CVE-2026-64160CVSS 9.8In the Linux kernel, the following vulnerability has been resolved: netfs: Fix potential for tearing in ->remote_i_size and ->zero_point Fix potential tearing in using ->remote_i_size and ->zero_point by copying i_size_read() and i_size_write() and using the same seqcount as for i_size. We need to make sure that netfslib and the filesystems that use it always hold i_lock whilst updating any of the sizes to prevent i_size_seqcount from getting corrupted.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-98490. Free for 1 server.

Get started free