Linux · SUSE Linux Enterprise · Security advisory · June 12, 2025
SUSE-SU-2025:01919-1: Security update for 4 packages
SUSE-SU-2025:01919-1, released June 12, 2025, fixes 427 CVEs across 4 products. None of them is reported as exploited. Patch Radar priority: Urgent.
Urgent
CVEs closed
427
3 rated Critical
Exploited
0
None reported
Highest CVSS
9.8
Base score, 0 to 10
Highest EPSS
0.3800
98th percentile
Priority of the 427 CVEs
Patch now 0
Urgent 3
High 172
Routine 252
Fixed package versions
| Product | Release | Fixed in |
|---|---|---|
| kernel-coco | sles 15.6 | 6.4.0-15061.21.coco15sp6.1 |
| kernel-coco_debug | sles 15.6 | 6.4.0-15061.21.coco15sp6.1 |
| kernel-source-coco | sles 15.6 | 6.4.0-15061.21.coco15sp6.1 |
| kernel-syms-coco | sles 15.6 | 6.4.0-15061.21.coco15sp6.1 |
CVEs this fix closes
| Priority | CVE | Title | CVSS | EPSS | Exploitation |
|---|---|---|---|---|---|
| Urgent | CVE-2024-53177 | kernel-64kb: smb: prevent use-after-free due to open_cached_dir error paths (bsc#1234896). | 9.8 | 0.0055 | None reported |
| Urgent | CVE-2025-22088 | kernel-64kb: Security update for the Linux Kernel | 9.8 | 0.0055 | None reported |
| Urgent | CVE-2025-21858 | kernel-64kb: Security update for the Linux Kernel | 8.8 | 0.0025 | None reported |
| High | CVE-2025-21760 | kernel-64kb: ndisc: extend RCU protection in ndisc_send_skb() (bsc#1238763). | 8.1 | 0.3800 | None reported |
| High | CVE-2025-21759 | kernel-64kb: ipv6: mcast: extend RCU protection in igmp6_send() (bsc#1238738). | 7.8 | 0.0780 | None reported |
| High | CVE-2025-21756 | kernel-64kb: Security update for the Linux Kernel | 7.8 | 0.0089 | None reported |
| High | CVE-2024-50083 | kernel-64kb: Security update for the Linux Kernel | 7.5 | 0.0087 | None reported |
| High | CVE-2025-37879 | 9p/net: fix improper handling of bogus negative read/write replies | 7.1 | 0.0073 | None reported |
| High | CVE-2025-21796 | kernel-64kb: Security update for the Linux Kernel | 9.8 | 0.0067 | None reported |
| High | CVE-2025-21795 | kernel: kernel: NFSD: fix hang in nfsd4_shutdown_callback | 7.8 | 0.0067 | None reported |
| High | CVE-2025-21762 | kernel-64kb: arp: use RCU protection in arp_xmit() (bsc#1238780). | 8.1 | 0.0066 | None reported |
| High | CVE-2024-27018 | kernel-64kb: Security update for the Linux Kernel | 7.8 | 0.0064 | None reported |
| High | CVE-2025-21927 | nvme-tcp: fix potential memory corruption in nvme_tcp_recv_pdu() | 8.0 | 0.0062 | None reported |
| High | CVE-2025-21844 | kernel-64kb: smb: client: Add check for next_buffer in receive_encrypted_standard() (bsc#1239512). | 7.8 | 0.0062 | None reported |
| High | CVE-2024-56640 | kernel-64kb: net/smc: fix LGR and link use-after-free issue (bsc#1235436). | 7.8 | 0.0062 | None reported |
| High | CVE-2025-21765 | kernel-64kb: ipv6: use RCU protection in ip6_default_advmss() (bsc#1237906). | 7.8 | 0.0061 | None reported |
| High | CVE-2024-46736 | dtb-aarch64: Security update for the Linux Kernel | 7.8 | 0.0061 | None reported |
| High | CVE-2024-46865 | kernel-64kb: Security update for the Linux Kernel | 7.1 | 0.0055 | None reported |
| High | CVE-2025-37750 | smb: client: fix UAF in decryption with multichannel | 7.8 | 0.0050 | None reported |
| High | CVE-2024-46796 | dtb-aarch64: Security update for the Linux Kernel | 7.8 | 0.0044 | None reported |
| High | CVE-2025-21855 | kernel-64kb: Security update for the Linux Kernel | 7.8 | 0.0044 | None reported |
| High | CVE-2024-28956 | kernel-64kb: x86/ibt: Keep IBT disabled during alternative patching (bsc#1242006). | 7.8 | 0.0043 | None reported |
| High | CVE-2025-21829 | kernel-64kb: Security update for the Linux Kernel | 7.8 | 0.0041 | None reported |
| High | CVE-2025-37749 | net: ppp: Add bound checking for skb data on ppp_sync_txmung | 7.8 | 0.0041 | None reported |
| High | CVE-2025-21735 | kernel-64kb: Security update for the Linux Kernel | 7.8 | 0.0038 | None reported |
Showing 1 to 25 of 427
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.