Linux · SUSE Linux Enterprise · Security advisory · June 5, 2026

SUSE-SU-2026:22087-1: Security update for 10 packages

SUSE-SU-2026:22087-1, released June 5, 2026, fixes 37 CVEs across 10 products. None of them is reported as exploited. Patch Radar priority: High.

High
CVEs closed
37
None rated Critical
Exploited
0
None reported
Highest CVSS
9.8
Base score, 0 to 10
Highest EPSS
0.0537
92nd percentile

Priority of the 37 CVEs

Patch now 0 Urgent 0 High 20 Routine 17

Fixed package versions

ProductReleaseFixed in
kernel-64kbsles 16.06.12.0-160000.34.1
kernel-azuresles 16.06.12.0-160000.34.1
kernel-defaultsles 16.06.12.0-160000.34.1
kernel-default-basesles 16.06.12.0-160000.34.1.160000.2.15
kernel-docssles 16.06.12.0-160000.34.1
kernel-kvmsmallsles 16.06.12.0-160000.34.1
kernel-obs-qasles 16.06.12.0-160000.34.1
kernel-sourcesles 16.06.12.0-160000.34.1
kernel-symssles 16.06.12.0-160000.34.1
kernel-zfcpdumpsles 16.06.12.0-160000.34.1

CVEs this fix closes

PriorityCVETitleCVSSEPSSExploitation
High CVE-2026-43499 rtmutex: Use waiter::task instead of current in remove_waiter()7.8 0.0537 None reported
High CVE-2026-43414 scsi: qla2xxx: Completely fix fcport double free9.8 0.0060 None reported
High CVE-2026-43341 kernel-64kb: net/ipv6: ioam6: prevent schema length wraparound in trace fill (bsc#1265044).9.8 0.0051 None reported
High CVE-2026-46110 kernel-64kb: net: stmmac: rename STMMAC_GET_ENTRY() -> STMMAC_NEXT_ENTRY() (bsc#1266759).7.5 0.0051 None reported
High CVE-2026-46243 smb: client: reject userspace cifs.spnego descriptions7.8 0.0041 None reported
High CVE-2026-45843 slip: bound decode() reads against the compressed packet length8.2 0.0040 None reported
High CVE-2026-31613 smb: client: fix OOB reads parsing symlink error response8.8 0.0039 None reported
High CVE-2026-43112 kernel-64kb: fs/smb/client: fix out-of-bounds read in cifs_sanitize_prepath (bsc#1264437).8.8 0.0035 None reported
High CVE-2026-31464 scsi: ibmvfc: Fix OOB access in ibmvfc_discover_targets_done()8.1 0.0028 None reported
High CVE-2026-43362 kernel-64kb: smb: client: fix in-place encryption corruption in SMB2_write() (bsc#1264989).8.1 0.0026 None reported
High CVE-2026-43009 bpf: Fix incorrect pruning due to atomic fetch precision tracking7.8 0.0016 None reported
High CVE-2026-31493 RDMA/efa: Fix use of completion ctx after free7.8 0.0016 None reported
High CVE-2026-31568 s390/mm: Add missing secure storage access fixups for donated memory7.1 0.0016 None reported
High CVE-2026-23444 wifi: mac80211: always free skb on ieee80211_tx_prepare_skb() failure7.1 0.0014 None reported
High CVE-2026-23359 bpf: Fix stack-out-of-bounds write in devmap7.8 0.0014 None reported
High CVE-2026-31729 usb: typec: ucsi: validate connector number in ucsi_notify_common()7.8 0.0013 None reported
High CVE-2026-43328 kernel-64kb: cpufreq: governor: Free dbs_data directly when gov->init() fails (bsc#1264832).7.8 0.0013 None reported
High CVE-2026-31521 module: Fix kernel panic when a symbol st_shndx is out of bounds7.0 0.0013 None reported
High CVE-2026-31614 kernel-64kb: smb: client: fix off-by-8 bounds check in check_wsl_eas() (bsc#1263774).7.1 0.0013 None reported
High CVE-2026-31516 xfrm: prevent policy_hthresh.work from racing with netns teardown7.8 0.0010 None reported
Routine CVE-2026-3150 kernel-64kb: bcache: fix cached_dev.sb_bio use-after-free and crash (bsc#1263169).n/a 0.0030 None reported
Routine CVE-2026-43360 kernel-64kb: btrfs: fix transaction abort on file creation due to name hash collision (bsc#1264720).5.5 0.0016 None reported
Routine CVE-2026-43234 team: avoid NETDEV_CHANGEMTU event when unregistering slave5.5 0.0016 None reported
Routine CVE-2026-43013 kernel-64kb: net/mlx5: lag: Check for LAG device before creating debugfs (bsc#1264011).5.5 0.0012 None reported
Routine CVE-2026-43333 kernel-64kb: bpf: reject direct access to nullable PTR_TO_BUF pointers (bsc#1264726).5.5 0.0012 None reported
Showing 1 to 25 of 37 1Next

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.