RHSA-2026:47017: kernel security update

RHSA-2026:47017, released June 26, 2026, fixes 3 CVEs in kernel (version 6.12.0-211.40.1.el10_2). None of them is reported as exploited. Patch Radar priority: High.

High

CVEs closed

None rated Critical

Exploited

None reported

Highest CVSS

8.8

Base score, 0 to 10

Highest EPSS

0.0113

66th percentile

Priority of the 3 CVEs

Patch now 0
                                Urgent 0
                                High 3
                                Routine 0

Fixed package versions

Product	Release	Fixed in
kernel	RHEL 10	6.12.0-211.40.1.el10_2

CVEs this fix closes

Priority	CVE	Title	CVSS	EPSS	Exploitation
High	CVE-2026-31635	kernel: In the Linux kernel, the following vulnerability has been resolved: rxrpc: fix oversized RESPONSE authenticator lengt...	7.8	0.0113	None reported
High	CVE-2026-53281	kernel: In the Linux kernel, the following vulnerability has been resolved: iommu/vt-d: Avoid NULL pointer dereference or ref...	8.8	0.0014	None reported
High	CVE-2026-46086	net: bridge: use a stable FDB dst snapshot in RCU readers	7.8	0.0013	None reported

Also fixes CVE-2026-31635

ALSA-2026:47017
kernel, kernel-64k, kernel-64k-core and 72 more on almalinux 10
DEBIAN-CVE-2026-31635
linux on Debian 14

Vendor advisory

https://access.redhat.com/errata/RHSA-2026:47017

For tools and AI agents

This page as data: JSON · Markdown

Link to this page

If this page saved you time, a link to it in your ticket, advisory or write-up helps others find it.

HTML

<a href="https://patchblox.com/security/fix/linux/rhsa-2026-47017">RHSA-2026:47017 on Patchblox Patch Radar</a>

Reusing the data? How to credit Patch Radar.

Which servers are still behind?

Patchblox compares the installed package on every Linux machine against the fixed version for its release, including machines reported through Azure Update Manager.

Get a demo

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.