USN-7610-3: linux-lowlatency-hwe-6.11 Ubuntu

CVSS: UnknownPublished

Published 15-07-2025Last modified 31-07-2026

Open JSON

Vulnerability summary

USN-7610-3 is a vulnerability in linux-lowlatency-hwe-6.11 Ubuntu with no CVSS score yet.

Overall risk

0/100

0100

Minimal · default modelHow is this calculated?

CVSS score

Not scored

010

No CVSS score recorded

EPSS score

Not scored

0%100%

No EPSS score yet

KEVNot listedIn no KEV catalog

RansomwareNone recordedNo known use recorded

Public exploits0No public exploits recorded

Advisory lineage

Upstream 6 · Downstream 0 · Related 6

CVE-2025-37798 CVE-2025-37890 CVE-2025-37932 CVE-2025-37997 CVE-2025-38000 CVE-2025-38001

Timeline

15-07-2025
PublishedVulnerability first disclosed.
31-07-2026
Last modifiedVulnerability information updated.

Description

linux-lowlatency-hwe-6.11 vulnerabilities Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems: - Netfilter; - Network traffic control; (CVE-2025-38001, CVE-2025-37997, CVE-2025-37798, CVE-2025-38000, CVE-2025-37932, CVE-2025-37890)

CVSS metrics

Risk metrics not yet published.

EPSS trend

No EPSS score has been published for this record yet.

Known exploited

Compare KEV catalogs

Not in any of the 3 tracked catalogs.

Public exploits

0 found

No public exploits indexed.

Weaknesses

CWE · root cause

No weakness data has been published for this record.

Affected systems

Ubuntu1 product

linux-lowlatency-hwe-6.11< 6.11.0-1016.17~24.04.1

1 vendor · 1 product

References

7 links

ubuntu.com/security/notices/USN-7610-3Advisory
ubuntu.com/security/CVE-2025-37798REPORT
ubuntu.com/security/CVE-2025-37890REPORT
ubuntu.com/security/CVE-2025-37932REPORT
ubuntu.com/security/CVE-2025-37997REPORT
ubuntu.com/security/CVE-2025-38000REPORT
ubuntu.com/security/CVE-2025-38001REPORT

Related vulnerabilities

USN-7445-1ubuntulinux-hwe-6.11+21y ago23-04-2025 12:12linux, linux-aws, linux-gcp, linux-hwe-6.11, linux-lowlatency, linux-lowlatency-hwe-6.11, linux-oem-6.11, linux-oracle, linux-raspi, linux-realtime vulnerabilities Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems: - GPIO subsystem; - GPU drivers; - IRQ chip drivers; - Network drivers; - Mellanox network drivers; - x86 platform drivers; - i.MX PM domains; - SCSI subsystem; - USB Serial drivers; - AFS file system; - GFS2 file system; - File systems infrastructure; - Proc file system; - SMB network file system; - Timer subsystem; - Kernel CPU control infrastructure; - Memory management; - Networking core; - Ethtool driver; - IEEE 802.15.4 subsystem; - Open vSwitch; - Network traffic control; - VMware vSockets driver; (CVE-2025-21685, CVE-2025-21684, CVE-2025-21756, CVE-2025-21670, CVE-2024-57949, CVE-2025-21677, CVE-2025-21680, CVE-2025-21703, CVE-2024-57952, CVE-2025-21674, CVE-2025-21701, CVE-2025-21691, CVE-2025-21689, CVE-2025-21668, CVE-2025-21665, CVE-2025-21683, CVE-2025-21675, CVE-2025-21672, CVE-2024-57948, CVE-2025-21669, CVE-2025-21673, CVE-2025-21692, CVE-2025-21699, CVE-2025-21702, CVE-2025-21682, CVE-2025-21690, CVE-2025-21681, CVE-2025-21695, CVE-2025-21696, CVE-2025-21700, CVE-2025-21678, CVE-2025-21676, CVE-2024-57950, CVE-2025-21666, CVE-2025-21694, CVE-2025-21693, CVE-2025-21993, CVE-2024-57951, CVE-2025-21697, CVE-2025-21667)USN-7381-1ubuntulinux-lowlatency-hwe-6.111y ago27-03-2025 17:07linux-lowlatency-hwe-6.11 vulnerabilities Attila Szász discovered that the HFS+ file system implementation in the Linux Kernel contained a heap overflow vulnerability. An attacker could use a specially crafted file system image that, when mounted, could cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2025-0927) Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems: - ARM64 architecture; - MIPS architecture; - PowerPC architecture; - RISC-V architecture; - S390 architecture; - x86 architecture; - Block layer subsystem; - Compute Acceleration Framework; - ACPI drivers; - Drivers core; - Ublk userspace block driver; - Virtio block driver; - Bluetooth drivers; - Buffer Sharing and Synchronization framework; - DMA engine subsystem; - EFI core; - GPIO subsystem; - GPU drivers; - HID subsystem; - Microsoft Hyper-V drivers; - Hardware monitoring drivers; - I3C subsystem; - IIO ADC drivers; - IIO subsystem; - InfiniBand drivers; - IOMMU subsystem; - LED subsystem; - Multiple devices driver; - Media drivers; - Microchip PCI driver; - MTD block device drivers; - Network drivers; - Mellanox network drivers; - STMicroelectronics network drivers; - NVME drivers; - PCI subsystem; - PHY drivers; - Pin controllers subsystem; - x86 platform drivers; - i.MX PM domains; - Power supply drivers; - Voltage and Current Regulator drivers; - SCSI subsystem; - i.MX SoC drivers; - SPI subsystem; - UFS subsystem; - USB Gadget drivers; - TDX Guest driver; - AFS file system; - BTRFS file system; - Ceph distributed file system; - File systems infrastructure; - F2FS file system; - JFFS2 file system; - JFS file system; - Network file systems library; - Network file system (NFS) server daemon; - NILFS2 file system; - File system notification infrastructure; - Overlay file system; - Diskquota system; - SMB network file system; - DRM display driver; - BPF subsystem; - VLANs driver; - KASAN memory debugging framework; - Memory management; - StackDepot library; - Bluetooth subsystem; - LAPB network protocol; - Network namespace; - Netfilter; - io_uring subsystem; - Control group (cgroup); - DMA mapping infrastructure; - KCSAN framework; - Scheduler infrastructure; - Seccomp subsystem; - Tracing infrastructure; - Workqueue subsystem; - KUnit library; - CAN network layer; - Networking core; - DCCP (Datagram Congestion Control Protocol); - HSR network protocol; - IEEE802154.4 network protocol; - IPv4 networking; - IPv6 networking; - MAC80211 subsystem; - Multipath TCP; - NET/ROM layer; - Packet sockets; - RDS protocol; - Network traffic control; - SCTP protocol; - SMC sockets; - TIPC protocol; - Wireless networking; - eXpress Data Path; - SELinux security module; - ALSA framework; - Intel ASoC drivers; - SOF drivers; (CVE-2024-56712, CVE-2024-56761, CVE-2025-21661, CVE-2024-56565, CVE-2024-57804, CVE-2024-57887, CVE-2025-21642, CVE-2024-56779, CVE-2025-21656, CVE-2024-57890, CVE-2024-36476, CVE-2024-57843, CVE-2024-56594, CVE-2024-41932, CVE-2025-21653, CVE-2024-56567, CVE-2024-56665, CVE-2024-54191, CVE-2024-57893, CVE-2024-57932, CVE-2024-56656, CVE-2024-57945, CVE-2024-57931, CVE-2024-56599, CVE-2024-57897, CVE-2024-57903, CVE-2024-57918, CVE-2024-57795, CVE-2024-56662, CVE-2025-21639, CVE-2024-55881, CVE-2024-57889, CVE-2024-57884, CVE-2024-57934, CVE-2024-39282, CVE-2024-56718, CVE-2024-56644, CVE-2024-56760, CVE-2024-43098, CVE-2024-47143, CVE-2024-55642, CVE-2024-56634, CVE-2024-56564, CVE-2024-56768, CVE-2024-56649, CVE-2024-57919, CVE-2024-56620, CVE-2024-56625, CVE-2024-56655, CVE-2024-56772, CVE-2025-21637, CVE-2024-56617, CVE-2024-57879, CVE-2024-56715, CVE-2024-56550, CVE-2024-50051, CVE-2024-56673, CVE-2024-51729, CVE-2025-21664, CVE-2025-21649, CVE-2024-56605, CVE-2024-56622, CVE-2024-56591, CVE-2024-56782, CVE-2024-57801, CVE-2024-56664, CVE-2024-57916, CVE-2024-53680, CVE-2024-57926, CVE-2024-56637, CVE-2024-56769, CVE-2024-57924, CVE-2024-56648, CVE-2024-57872, CVE-2024-56593, CVE-2024-57913, CVE-2024-53682, CVE-2024-56670, CVE-2024-56767, CVE-2024-56778, CVE-2024-56777, CVE-2025-21658, CVE-2025-21646, CVE-2024-48875, CVE-2024-56758, CVE-2024-56604, CVE-2024-56787, CVE-2024-56581, CVE-2025-21635, CVE-2024-56641, CVE-2024-56608, CVE-2024-57885, CVE-2024-56716, CVE-2024-56671, CVE-2024-56559, CVE-2025-21633, CVE-2024-56372, CVE-2024-57888, CVE-2024-56623, CVE-2025-21638, CVE-2024-56600, CVE-2024-56647, CVE-2025-21659, CVE-2024-41935, CVE-2024-56624, CVE-2024-56574, CVE-2025-21648, CVE-2024-56621, CVE-2024-54460, CVE-2024-56659, CVE-2024-47141, CVE-2024-57805, CVE-2024-57792, CVE-2024-45828, CVE-2024-53681, CVE-2024-56568, CVE-2024-56764, CVE-2025-21650, CVE-2024-56601, CVE-2024-56663, CVE-2025-21660, CVE-2025-21629, CVE-2024-56595, CVE-2024-57917, CVE-2024-53685, CVE-2024-57882, CVE-2024-57894, CVE-2024-56651, CVE-2024-56657, CVE-2024-57876, CVE-2024-56717, CVE-2024-57935, CVE-2024-56667, CVE-2024-57910, CVE-2024-57793, CVE-2024-56631, CVE-2024-56638, CVE-2025-21640, CVE-2024-56710, CVE-2024-56583, CVE-2024-56557, CVE-2024-56658, CVE-2025-21632, CVE-2024-56645, CVE-2024-56646, CVE-2024-56640, CVE-2024-57944, CVE-2024-56598, CVE-2024-57857, CVE-2024-56709, CVE-2024-56654, CVE-2024-57809, CVE-2024-57895, CVE-2025-21834, CVE-2024-56763, CVE-2024-48881, CVE-2024-57841, CVE-2024-57878, CVE-2024-56774, CVE-2024-57791, CVE-2024-56575, CVE-2024-56619, CVE-2024-56570, CVE-2024-56616, CVE-2024-56569, CVE-2025-21636, CVE-2024-56572, CVE-2024-56552, CVE-2024-56596, CVE-2025-21654, CVE-2024-56573, CVE-2024-56784, CVE-2024-56626, CVE-2024-56642, CVE-2024-56643, CVE-2024-56719, CVE-2024-56632, CVE-2024-57839, CVE-2024-56578, CVE-2024-53690, CVE-2024-56609, CVE-2024-56562, CVE-2024-56589, CVE-2024-56781, CVE-2024-56672, CVE-2024-56775, CVE-2024-56713, CVE-2024-56580, CVE-2024-57874, CVE-2024-56369, CVE-2024-56711, CVE-2025-21651, CVE-2024-56584, CVE-2024-57904, CVE-2024-54680, CVE-2024-56577, CVE-2024-56558, CVE-2024-56780, CVE-2024-58087, CVE-2024-57892, CVE-2025-21644, CVE-2024-57911, CVE-2024-56579, CVE-2025-21663, CVE-2024-56618, CVE-2024-56766, CVE-2024-56653, CVE-2025-21655, CVE-2024-56669, CVE-2024-56759, CVE-2024-48876, CVE-2025-21631, CVE-2024-56765, CVE-2024-56770, CVE-2024-57838, CVE-2025-21634, CVE-2024-56650, CVE-2024-57939, CVE-2024-56606, CVE-2024-56610, CVE-2025-21662, CVE-2024-56785, CVE-2024-55916, CVE-2025-21643, CVE-2024-56586, CVE-2024-56582, CVE-2024-56614, CVE-2024-49571, CVE-2024-49569, CVE-2024-57798, CVE-2024-56633, CVE-2024-55641, CVE-2025-21647, CVE-2025-21652, CVE-2024-56757, CVE-2024-56597, CVE-2024-47794, CVE-2024-57902, CVE-2024-57925, CVE-2024-54683, CVE-2024-57938, CVE-2024-56615, CVE-2024-57906, CVE-2024-53687, CVE-2024-57899, CVE-2024-56783, CVE-2024-56786, CVE-2024-56635, CVE-2024-56551, CVE-2024-53179, CVE-2024-56588, CVE-2024-47408, CVE-2024-57849, CVE-2024-52319, CVE-2024-56576, CVE-2024-57905, CVE-2024-57946, CVE-2024-56607, CVE-2024-57806, CVE-2024-57933, CVE-2024-55639, CVE-2024-56561, CVE-2024-48873, CVE-2024-52332, CVE-2025-21645, CVE-2024-56602, CVE-2024-56590, CVE-2024-57799, CVE-2024-57929, CVE-2024-56639, CVE-2024-56613, CVE-2024-56675, CVE-2024-57912, CVE-2024-57883, CVE-2024-56636, CVE-2024-56592, CVE-2024-57802, CVE-2024-54455, CVE-2024-57908, CVE-2024-56603, CVE-2024-57875, CVE-2024-56773, CVE-2024-47809, CVE-2024-56630, CVE-2024-56587, CVE-2024-56627, CVE-2024-57921, CVE-2024-56660, CVE-2024-56771, CVE-2024-57886, CVE-2024-57896, CVE-2024-57807, CVE-2024-57907, CVE-2024-49568, CVE-2024-54193, CVE-2024-56652, CVE-2024-57940, CVE-2024-57898, CVE-2024-57901, CVE-2024-56714, CVE-2024-56566, CVE-2024-56563, CVE-2024-56368, CVE-2024-56611, CVE-2024-56776, CVE-2024-57850, CVE-2024-56629, CVE-2024-57881, CVE-2024-57880, CVE-2024-57900)CVE-2025-21815debianlinux+1080.19%1y ago27-02-2025 20:04In the Linux kernel, the following vulnerability has been resolved: mm/compaction: fix UBSAN shift-out-of-bounds warning syzkaller reported a UBSAN shift-out-of-bounds warning of (1UL << order) in isolate_freepages_block(). The bogus compound_order can be any value because it is union with flags. Add back the MAX_PAGE_ORDER check to fix the warning.CVE-2025-21725debianlinux+1110.40%1y ago27-02-2025 02:07In the Linux kernel, the following vulnerability has been resolved: smb: client: fix oops due to unset link speed It isn't guaranteed that NETWORK_INTERFACE_INFO::LinkSpeed will always be set by the server, so the client must handle any values and then prevent oopses like below from happening: Oops: divide error: 0000 [#1] PREEMPT SMP KASAN NOPTI CPU: 0 UID: 0 PID: 1323 Comm: cat Not tainted 6.13.0-rc7 #2 Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-3.fc41 04/01/2014 RIP: 0010:cifs_debug_data_proc_show+0xa45/0x1460 [cifs] Code: 00 00 48 89 df e8 3b cd 1b c1 41 f6 44 24 2c 04 0f 84 50 01 00 00 48 89 ef e8 e7 d0 1b c1 49 8b 44 24 18 31 d2 49 8d 7c 24 28 <48> f7 74 24 18 48 89 c3 e8 6e cf 1b c1 41 8b 6c 24 28 49 8d 7c 24 RSP: 0018:ffffc90001817be0 EFLAGS: 00010246 RAX: 0000000000000000 RBX: ffff88811230022c RCX: ffffffffc041bd99 RDX: 0000000000000000 RSI: 0000000000000567 RDI: ffff888112300228 RBP: ffff888112300218 R08: fffff52000302f5f R09: ffffed1022fa58ac R10: ffff888117d2c566 R11: 00000000fffffffe R12: ffff888112300200 R13: 000000012a15343f R14: 0000000000000001 R15: ffff888113f2db58 FS: 00007fe27119e740(0000) GS:ffff888148600000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fe2633c5000 CR3: 0000000124da0000 CR4: 0000000000750ef0 PKRU: 55555554 Call Trace: <TASK> ? __die_body.cold+0x19/0x27 ? die+0x2e/0x50 ? do_trap+0x159/0x1b0 ? cifs_debug_data_proc_show+0xa45/0x1460 [cifs] ? do_error_trap+0x90/0x130 ? cifs_debug_data_proc_show+0xa45/0x1460 [cifs] ? exc_divide_error+0x39/0x50 ? cifs_debug_data_proc_show+0xa45/0x1460 [cifs] ? asm_exc_divide_error+0x1a/0x20 ? cifs_debug_data_proc_show+0xa39/0x1460 [cifs] ? cifs_debug_data_proc_show+0xa45/0x1460 [cifs] ? seq_read_iter+0x42e/0x790 seq_read_iter+0x19a/0x790 proc_reg_read_iter+0xbe/0x110 ? __pfx_proc_reg_read_iter+0x10/0x10 vfs_read+0x469/0x570 ? do_user_addr_fault+0x398/0x760 ? __pfx_vfs_read+0x10/0x10 ? find_held_lock+0x8a/0xa0 ? __pfx_lock_release+0x10/0x10 ksys_read+0xd3/0x170 ? __pfx_ksys_read+0x10/0x10 ? __rcu_read_unlock+0x50/0x270 ? mark_held_locks+0x1a/0x90 do_syscall_64+0xbb/0x1d0 entry_SYSCALL_64_after_hwframe+0x77/0x7f RIP: 0033:0x7fe271288911 Code: 00 48 8b 15 01 25 10 00 f7 d8 64 89 02 b8 ff ff ff ff eb bd e8 20 ad 01 00 f3 0f 1e fa 80 3d b5 a7 10 00 00 74 13 31 c0 0f 05 <48> 3d 00 f0 ff ff 77 4f c3 66 0f 1f 44 00 00 55 48 89 e5 48 83 ec RSP: 002b:00007ffe87c079d8 EFLAGS: 00000246 ORIG_RAX: 0000000000000000 RAX: ffffffffffffffda RBX: 0000000000040000 RCX: 00007fe271288911 RDX: 0000000000040000 RSI: 00007fe2633c6000 RDI: 0000000000000003 RBP: 00007ffe87c07a00 R08: 0000000000000000 R09: 00007fe2713e6380 R10: 0000000000000022 R11: 0000000000000246 R12: 0000000000040000 R13: 00007fe2633c6000 R14: 0000000000000003 R15: 0000000000000000 </TASK> Fix this by setting cifs_server_iface::speed to a sane value (1Gbps) by default when link speed is unset.CVE-2025-21748debianlinux+1260.61%1y ago27-02-2025 02:12In the Linux kernel, the following vulnerability has been resolved: ksmbd: fix integer overflows on 32 bit systems On 32bit systems the addition operations in ipc_msg_alloc() can potentially overflow leading to memory corruption. Add bounds checking using KSMBD_IPC_MAX_PAYLOAD to avoid overflow.CVE-2025-21666debianlinux+1260.22%1y ago31-01-2025 11:25In the Linux kernel, the following vulnerability has been resolved: vsock: prevent null-ptr-deref in vsock_*[has_data|has_space] Recent reports have shown how we sometimes call vsock_*_has_data() when a vsock socket has been de-assigned from a transport (see attached links), but we shouldn't. Previous commits should have solved the real problems, but we may have more in the future, so to avoid null-ptr-deref, we can return 0 (no space, no data available) but with a warning. This way the code should continue to run in a nearly consistent state and have a warning that allows us to debug future problems.