Search/selinux
● Vendor

selinux

Known CVEs
0
Highest CVSS
—
In KEV
0
Vendor
setroubleshoot
Connections
24 relationships
USN-8618-1: Linux kernel vulnerabilities
It was discovered that some AMD Zen 2 processors did not properly isolate shared resources in the operation cache. A local attacker could possibly use this issue to corrupt instructions executed at a higher privilege level, resulting in privilege escalation. (CVE-2025-54518) 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: - x86 platform drivers; - Cryptographic API; - PSP security protocol; - ARM32 architecture; - ARM64 architecture; - MIPS architecture; - PowerPC architecture; - RISC-V architecture; - S390 architecture; - User-Mode Linux (UML); - x86 architecture; - Block layer subsystem; - Intel NPU Driver; - Compute Acceleration Framework; - ACPI drivers; - Auxiliary display drivers; - Drivers core; - DRBD Distributed Replicated Block Device drivers; - Rados block device (RBD) driver; - Ublk userspace block driver; - Compressed RAM block device driver; - Bluetooth drivers; - Bus devices; - Character device driver; - Clock framework and drivers; - CPU frequency scaling framework; - Hardware crypto device drivers; - Buffer Sharing and Synchronization framework; - DPLL subsystem; - EDAC drivers; - Arm Firmware Framework for ARMv8-A(FFA); - EFI core; - FWCTL subsystem; - GPIO subsystem; - GPU drivers; - HID subsystem; - Hardware monitoring drivers; - I2C subsystem; - I3C subsystem; - IIO ADC drivers; - IIO subsystem; - InfiniBand drivers; - Input Device core drivers; - Input Device (Mouse) drivers; - IOMMU subsystem; - Mailbox framework; - Multiple devices driver; - Media drivers; - NVIDIA Tegra memory controller driver; - MTD block device drivers; - Network drivers; - Ethernet bonding driver; - Mellanox network drivers; - Microsoft Azure Network Adapter (MANA) driver; - STMicroelectronics network drivers; - Texas Instruments network drivers; - MediaTek network drivers; - NVME drivers; - Parport drivers; - PCI subsystem; - PHY drivers; - Pin controllers subsystem; - Chrome hardware platform drivers; - ACPI WMI driver; - Generic PM domains; - MediaTek PM domains; - Power supply drivers; - Voltage and Current Regulator drivers; - MPAM driver; - Amlogic Meson reset controller drivers; - S/390 drivers; - SCSI subsystem; - NVIDIA Tegra Control Backbone (CBB) driver; - SPI subsystem; - Greybus lights staging drivers; - Media staging drivers; - Realtek RTL8723BS SDIO drivers; - TCM subsystem; - Thunderbolt and USB4 drivers; - TTY drivers; - Userspace I/O drivers; - USB Device Class drivers; - ULPI bus; - DesignWare USB2 driver; - USB Gadget drivers; - USB Dual Role (OTG-ready) Controller drivers; - USB Serial drivers; - USB Type-C support driver; - USB Type-C Port Controller Manager driver; - TI TPS6598x USB Power Delivery controller driver; - USB Type-C Connector System Software Interface driver; - USB over IP driver; - vDPA drivers; - VFIO drivers; - Framebuffer layer; - TSM AMD SEV Guest driver; - Xen hypervisor drivers; - 9P distributed file system; - File systems infrastructure; - AFS file system; - BTRFS file system; - Ceph distributed file system; - EROFS file system; - F2FS file system; - FUSE (File system in Userspace); - GFS2 file system; - HFS+ file system; - HugeTLB file system; - Network file systems library; - Network file system (NFS) server daemon; - NILFS2 file system; - File system notification infrastructure; - NTFS3 file system; - OCFS2 file system; - Overlay file system; - Diskquota system; - SMB network file system; - Tracing file system; - UDF file system; - DRM TTM subsystem; - Control group (cgroup); - Kernel CPU control infrastructure; - Tracing infrastructure; - QorIQ DPAA2 FSL-MC bus driver; - Freescale ENETC Ethernet drivers; - Software nodes and device properties; - Memory management; - Memory Management; - Linked list library; - Netfilter; - padata parallel execution mechanism; - PPP protocol drivers and compressors; - Bluetooth subsystem; - Networking core; - Network shaper API; - Network traffic control; - TCP network protocol; - XFRM subsystem; - io_uring subsystem; - IPC subsystem; - Audit subsystem; - BPF subsystem; - DMA mapping infrastructure; - Kernel exit() syscall; - Kernel fork() syscall; - Kernel futex primitives; - IRQ subsystem; - Kexec HandOver (KHO); - Padata parallel execution mechanism; - RCU subsystem; - Scheduler infrastructure; - Cryptographic library; - KProbes tracing; - 802.1Q VLAN protocol; - B.A.T.M.A.N. meshing protocol; - Ethernet bridge; - Ceph Core library; - Distributed Switch Architecture; - Ethtool driver; - Handshake API; - HSR network protocol; - IPv4 networking; - IPv6 networking; - IUCV driver; - L2TP protocol; - MAC80211 subsystem; - Multipath TCP; - NFC subsystem; - Open vSwitch; - Phonet protocol; - RDS protocol; - RxRPC session sockets; - SCTP protocol; - SMC sockets; - TIPC protocol; - TLS protocol; - Unix domain sockets; - VMware vSockets driver; - Wireless networking; - Integrity Measurement Architecture(IMA) framework; - Key management; - Linux Security Modules (LSM) Framework; - SELinux security module; - ALSA framework; - HD-audio driver; - AudioScience HPI driver; - FourSemi audio codecs; - Texas InstrumentS Audio (ASoC/HDA) drivers; - Simple audio multiplexer codec driver; - QCOM ASoC drivers; - Renesas ASoC drivers; - SOF drivers; - STI ASoC drivers; - USB sound devices; - KVM subsystem; (CVE-2026-43490, CVE-2026-43492, CVE-2026-43495, CVE-2026-43496, CVE-2026-43497, CVE-2026-43498, CVE-2026-43502, CVE-2026-45834, CVE-2026-45835, CVE-2026-45836, CVE-2026-45837, CVE-2026-45838, CVE-2026-45839, CVE-2026-45840, CVE-2026-45841, CVE-2026-45842, CVE-2026-45843, CVE-2026-45844, CVE-2026-45845, CVE-2026-45846, CVE-2026-46104, CVE-2026-46105, CVE-2026-46106, CVE-2026-46107, CVE-2026-46108, CVE-2026-46109, CVE-2026-46110, CVE-2026-46111, CVE-2026-46112, CVE-2026-46113, CVE-2026-46114, CVE-2026-46116, CVE-2026-46117, CVE-2026-46118, CVE-2026-46120, CVE-2026-46121, CVE-2026-46122, CVE-2026-46123, CVE-2026-46124, CVE-2026-46125, CVE-2026-46126, CVE-2026-46127, CVE-2026-46128, CVE-2026-46129, CVE-2026-46130, CVE-2026-46131, CVE-2026-46132, CVE-2026-46133, CVE-2026-46134, CVE-2026-46136, CVE-2026-46138, CVE-2026-46139, CVE-2026-46140, CVE-2026-46141, CVE-2026-46142, CVE-2026-46143, CVE-2026-46144, CVE-2026-46145, CVE-2026-46146, CVE-2026-46147, CVE-2026-46148, CVE-2026-46149, CVE-2026-46150, CVE-2026-46151, CVE-2026-46152, CVE-2026-46153, CVE-2026-46154, CVE-2026-46156, CVE-2026-46157, CVE-2026-46158, CVE-2026-46159, CVE-2026-46160, CVE-2026-46161, CVE-2026-46162, CVE-2026-46163, CVE-2026-46164, CVE-2026-46165, CVE-2026-46166, CVE-2026-46167, CVE-2026-46168, CVE-2026-46169, CVE-2026-46170, CVE-2026-46171, CVE-2026-46172, CVE-2026-46173, CVE-2026-46174, CVE-2026-46175, CVE-2026-46176, CVE-2026-46177, CVE-2026-46178, CVE-2026-46179, CVE-2026-46180, CVE-2026-46181, CVE-2026-46182, CVE-2026-46183, CVE-2026-46184, CVE-2026-46186, CVE-2026-46187, CVE-2026-46188, CVE-2026-46189, CVE-2026-46190, CVE-2026-46191, CVE-2026-46192, CVE-2026-46193, CVE-2026-46194, CVE-2026-46196, CVE-2026-46197, CVE-2026-46198, CVE-2026-46199, CVE-2026-46200, CVE-2026-46201, CVE-2026-46202, CVE-2026-46203, CVE-2026-46204, CVE-2026-46205, CVE-2026-46206, CVE-2026-46207, CVE-2026-46208, CVE-2026-46209, CVE-2026-46210, CVE-2026-46211, CVE-2026-46212, CVE-2026-46213, CVE-2026-46214, CVE-2026-46215, CVE-2026-46216, CVE-2026-46218, CVE-2026-46219, CVE-2026-46220, CVE-2026-46221, CVE-2026-46222, CVE-2026-46223, CVE-2026-46224, CVE-2026-46225, CVE-2026-46226, CVE-2026-46227, CVE-2026-46228, CVE-2026-46229, CVE-2026-46230, CVE-2026-46231, CVE-2026-46232, CVE-2026-46233, CVE-2026-46234, CVE-2026-46235, CVE-2026-46236, CVE-2026-46238, CVE-2026-46239, CVE-2026-46240, CVE-2026-46241, CVE-2026-46242, CVE-2026-46273, CVE-2026-46274, CVE-2026-46275, CVE-2026-46290, CVE-2026-46291, CVE-2026-46292, CVE-2026-46293, CVE-2026-46294, CVE-2026-46295, CVE-2026-46296, CVE-2026-46297, CVE-2026-46298, CVE-2026-46299, CVE-2026-46301, CVE-2026-46302, CVE-2026-46303, CVE-2026-46304, CVE-2026-46305, CVE-2026-46306, CVE-2026-46307, CVE-2026-46308, CVE-2026-46309, CVE-2026-46310, CVE-2026-46311, CVE-2026-46312, CVE-2026-46313, CVE-2026-46314, CVE-2026-46315, CVE-2026-46317, CVE-2026-46318, CVE-2026-46319, CVE-2026-46320, CVE-2026-46321, CVE-2026-46322, CVE-2026-46324, CVE-2026-52911, CVE-2026-52912, CVE-2026-52913, CVE-2026-52914, CVE-2026-52915, CVE-2026-52916, CVE-2026-52918, CVE-2026-52919, CVE-2026-52920, CVE-2026-52921, CVE-2026-52922, CVE-2026-52923, CVE-2026-52925, CVE-2026-52926, CVE-2026-52927, CVE-2026-52928, CVE-2026-52931, CVE-2026-52932, CVE-2026-52934, CVE-2026-52936, CVE-2026-52937, CVE-2026-52941, CVE-2026-52943, CVE-2026-52944, CVE-2026-52949, CVE-2026-52950, CVE-2026-52951, CVE-2026-52952, CVE-2026-52953, CVE-2026-52954, CVE-2026-52955, CVE-2026-52956, CVE-2026-52957, CVE-2026-52958, CVE-2026-52959, CVE-2026-52960, CVE-2026-52961, CVE-2026-52962, CVE-2026-52963, CVE-2026-52964, CVE-2026-52965, CVE-2026-52967, CVE-2026-52968, CVE-2026-52969, CVE-2026-52970, CVE-2026-52971, CVE-2026-52973, CVE-2026-52974, CVE-2026-52975, CVE-2026-52976, CVE-2026-52977, CVE-2026-52978, CVE-2026-52979, CVE-2026-52980, CVE-2026-52981, CVE-2026-52982, CVE-2026-52983, CVE-2026-52984, CVE-2026-52985, CVE-2026-52986, CVE-2026-52987, CVE-2026-52988, CVE-2026-52989, CVE-2026-52990, CVE-2026-52991, CVE-2026-52992, CVE-2026-52993, CVE-2026-52994, CVE-2026-52995, CVE-2026-52996, CVE-2026-52997, CVE-2026-52998, CVE-2026-52999, CVE-2026-53000, CVE-2026-53001, CVE-2026-53002, CVE-2026-53003, CVE-2026-53004, CVE-2026-53005, CVE-2026-53006, CVE-2026-53007, CVE-2026-53008, CVE-2026-53009, CVE-2026-53010, CVE-2026-53011, CVE-2026-53012, CVE-2026-53013, CVE-2026-53014, CVE-2026-53015, CVE-2026-53016, CVE-2026-53017, CVE-2026-53018, CVE-2026-53019, CVE-2026-53020, CVE-2026-53021, CVE-2026-53022, CVE-2026-53023, CVE-2026-53024, CVE-2026-53025, CVE-2026-53026, CVE-2026-53027, CVE-2026-53028, CVE-2026-53029, CVE-2026-53030, CVE-2026-53031, CVE-2026-53032, CVE-2026-53033, CVE-2026-53034, CVE-2026-53035, CVE-2026-53036, CVE-2026-53037, CVE-2026-53038, CVE-2026-53039, CVE-2026-53040, CVE-2026-53041, CVE-2026-53042, CVE-2026-53043, CVE-2026-53044, CVE-2026-53045, CVE-2026-53046, CVE-2026-53047, CVE-2026-53048, CVE-2026-53049, CVE-2026-53050, CVE-2026-53051, CVE-2026-53052, CVE-2026-53053, CVE-2026-53054, CVE-2026-53055, CVE-2026-53056, CVE-2026-53057, CVE-2026-53058, CVE-2026-53059, CVE-2026-53060, CVE-2026-53061, CVE-2026-53062, CVE-2026-53063, CVE-2026-53064, CVE-2026-53065, CVE-2026-53066, CVE-2026-53067, CVE-2026-53068, CVE-2026-53069, CVE-2026-53070, CVE-2026-53071, CVE-2026-53072, CVE-2026-53073, CVE-2026-53074, CVE-2026-53075, CVE-2026-53076, CVE-2026-53077, CVE-2026-53078, CVE-2026-53079, CVE-2026-53080, CVE-2026-53081, CVE-2026-53082, CVE-2026-53083, CVE-2026-53084, CVE-2026-53085, CVE-2026-53086, CVE-2026-53087, CVE-2026-53088, CVE-2026-53089, CVE-2026-53090, CVE-2026-53091, CVE-2026-53092, CVE-2026-53093, CVE-2026-53094, CVE-2026-53095, CVE-2026-53096, CVE-2026-53097, CVE-2026-53098, CVE-2026-53099, CVE-2026-53100, CVE-2026-53101, CVE-2026-53102, CVE-2026-53103, CVE-2026-53104, CVE-2026-53105, CVE-2026-53106, CVE-2026-53107, CVE-2026-53108, CVE-2026-53109, CVE-2026-53110, CVE-2026-53111, CVE-2026-53112, CVE-2026-53113, CVE-2026-53114, CVE-2026-53115, CVE-2026-53116, CVE-2026-53117, CVE-2026-53118, CVE-2026-53119, CVE-2026-53120, CVE-2026-53121, CVE-2026-53122, CVE-2026-53123, CVE-2026-53124, CVE-2026-53125, CVE-2026-53126, CVE-2026-53127, CVE-2026-53128, CVE-2026-53129, CVE-2026-53130, CVE-2026-53174, CVE-2026-53277, CVE-2026-53278, CVE-2026-53279, CVE-2026-53280, CVE-2026-53281, CVE-2026-53282, CVE-2026-53283, CVE-2026-53284, CVE-2026-53285, CVE-2026-53286, CVE-2026-53287, CVE-2026-53288, CVE-2026-53289, CVE-2026-53290, CVE-2026-53291, CVE-2026-53292, CVE-2026-53293, CVE-2026-53294, CVE-2026-53295, CVE-2026-53296, CVE-2026-53297, CVE-2026-53298, CVE-2026-53299, CVE-2026-53300, CVE-2026-53301, CVE-2026-53302, CVE-2026-53303, CVE-2026-53304, CVE-2026-53305, CVE-2026-53306, CVE-2026-53307, CVE-2026-53308, CVE-2026-53309, CVE-2026-53310, CVE-2026-53311, CVE-2026-53312, CVE-2026-53313, CVE-2026-53314, CVE-2026-53315, CVE-2026-53316, CVE-2026-53317, CVE-2026-53318, CVE-2026-53319, CVE-2026-53320, CVE-2026-53321, CVE-2026-53322, CVE-2026-53323, CVE-2026-53324, CVE-2026-53357, CVE-2026-53358, CVE-2026-53360, CVE-2026-53364, CVE-2026-53365, CVE-2026-53367, CVE-2026-53368, CVE-2026-53369, CVE-2026-53370, CVE-2026-53371, CVE-2026-53372, CVE-2026-53373, CVE-2026-53374, CVE-2026-53375, CVE-2026-53376, CVE-2026-53377, CVE-2026-53378, CVE-2026-53379, CVE-2026-53380, CVE-2026-63837, CVE-2026-63838, CVE-2026-63839, CVE-2026-63840, CVE-2026-63841, CVE-2026-63842, CVE-2026-63843, CVE-2026-63844, CVE-2026-63845, CVE-2026-63846, CVE-2026-63847, CVE-2026-63848, CVE-2026-63849, CVE-2026-63850, CVE-2026-63851, CVE-2026-63852, CVE-2026-63853, CVE-2026-63854, CVE-2026-63855, CVE-2026-63856, CVE-2026-63857, CVE-2026-63858, CVE-2026-63859, CVE-2026-63860, CVE-2026-63861, CVE-2026-63862, CVE-2026-63863, CVE-2026-63864, CVE-2026-63865, CVE-2026-63866, CVE-2026-63875, CVE-2026-63876, CVE-2026-63877, CVE-2026-63878, CVE-2026-63879, CVE-2026-63880, CVE-2026-63881, CVE-2026-63882, CVE-2026-63883, CVE-2026-63884, CVE-2026-63886, CVE-2026-63887, CVE-2026-63888, CVE-2026-63889, CVE-2026-63890, CVE-2026-63891, CVE-2026-63892, CVE-2026-63893, CVE-2026-63894, CVE-2026-63895, CVE-2026-63896, CVE-2026-63897, CVE-2026-63898, CVE-2026-63899, CVE-2026-63900, CVE-2026-63901, CVE-2026-63902, CVE-2026-63903, CVE-2026-63904, CVE-2026-63905, CVE-2026-63906, CVE-2026-63907, CVE-2026-63908, CVE-2026-63909, CVE-2026-63910, CVE-2026-63911, CVE-2026-63912, CVE-2026-63913, CVE-2026-63914, CVE-2026-63915, CVE-2026-63916, CVE-2026-63917, CVE-2026-63918, CVE-2026-63919, CVE-2026-63920, CVE-2026-63921, CVE-2026-63922, CVE-2026-63923, CVE-2026-63924, CVE-2026-63925, CVE-2026-63926, CVE-2026-63927, CVE-2026-63928, CVE-2026-63929, CVE-2026-63930, CVE-2026-63931, CVE-2026-63932, CVE-2026-63933, CVE-2026-63934, CVE-2026-63935, CVE-2026-63936, CVE-2026-63937, CVE-2026-63938, CVE-2026-63939, CVE-2026-63940, CVE-2026-63941, CVE-2026-63942, CVE-2026-63943, CVE-2026-63944, CVE-2026-63945, CVE-2026-63946, CVE-2026-63947, CVE-2026-63948, CVE-2026-63949, CVE-2026-63950, CVE-2026-63951, CVE-2026-63952, CVE-2026-63953, CVE-2026-63954, CVE-2026-63955, CVE-2026-63956, CVE-2026-63957, CVE-2026-63958, CVE-2026-63959, CVE-2026-63960, CVE-2026-63961, CVE-2026-63962, CVE-2026-63963, CVE-2026-63964, CVE-2026-63965, CVE-2026-63966, CVE-2026-63967, CVE-2026-63968, CVE-2026-63969, CVE-2026-63970, CVE-2026-63971, CVE-2026-63972, CVE-2026-63973, CVE-2026-63974, CVE-2026-63975, CVE-2026-63976, CVE-2026-63977, CVE-2026-63978, CVE-2026-63979, CVE-2026-63980, CVE-2026-63981, CVE-2026-63982, CVE-2026-63983, CVE-2026-63984, CVE-2026-63985, CVE-2026-63986, CVE-2026-63987, CVE-2026-63988, CVE-2026-63989, CVE-2026-63990, CVE-2026-63991, CVE-2026-63992, CVE-2026-63993, CVE-2026-63994, CVE-2026-63995, CVE-2026-63996, CVE-2026-63997, CVE-2026-63998, CVE-2026-63999, CVE-2026-64000, CVE-2026-64001, CVE-2026-64002, CVE-2026-64003, CVE-2026-64004, CVE-2026-64005, CVE-2026-64006, CVE-2026-64007, CVE-2026-64008, CVE-2026-64009, CVE-2026-64010, CVE-2026-64011, CVE-2026-64012, CVE-2026-64013, CVE-2026-64014, CVE-2026-64015, CVE-2026-64017, CVE-2026-64018, CVE-2026-64019, CVE-2026-64020, CVE-2026-64021, CVE-2026-64022, CVE-2026-64023, CVE-2026-64024, CVE-2026-64025, CVE-2026-64026, CVE-2026-64027, CVE-2026-64029, CVE-2026-64030, CVE-2026-64031, CVE-2026-64032, CVE-2026-64033, CVE-2026-64034, CVE-2026-64035, CVE-2026-64036, CVE-2026-64037, CVE-2026-64038, CVE-2026-64039, CVE-2026-64040, CVE-2026-64041, CVE-2026-64042, CVE-2026-64043, CVE-2026-64044, CVE-2026-64045, CVE-2026-64046, CVE-2026-64047, CVE-2026-64048, CVE-2026-64049, CVE-2026-64050, CVE-2026-64051, CVE-2026-64052, CVE-2026-64053, CVE-2026-64054, CVE-2026-64055, CVE-2026-64056, CVE-2026-64057, CVE-2026-64058, CVE-2026-64059, CVE-2026-64060, CVE-2026-64061, CVE-2026-64062, CVE-2026-64063, CVE-2026-64064, CVE-2026-64065, CVE-2026-64066, CVE-2026-64067, CVE-2026-64068, CVE-2026-64069, CVE-2026-64070, CVE-2026-64071, CVE-2026-64072, CVE-2026-64073, CVE-2026-64074, CVE-2026-64075, CVE-2026-64076, CVE-2026-64077, CVE-2026-64078, CVE-2026-64079, CVE-2026-64080, CVE-2026-64081, CVE-2026-64082, CVE-2026-64083, CVE-2026-64084, CVE-2026-64085, CVE-2026-64086, CVE-2026-64087, CVE-2026-64088, CVE-2026-64089, CVE-2026-64090, CVE-2026-64091, CVE-2026-64093, CVE-2026-64094, CVE-2026-64095, CVE-2026-64096, CVE-2026-64097, CVE-2026-64098, CVE-2026-64099, CVE-2026-64100, CVE-2026-64101, CVE-2026-64102, CVE-2026-64103, CVE-2026-64104, CVE-2026-64105, CVE-2026-64106, CVE-2026-64107, CVE-2026-64108, CVE-2026-64109, CVE-2026-64110, CVE-2026-64111, CVE-2026-64112, CVE-2026-64113, CVE-2026-64114, CVE-2026-64115, CVE-2026-64116, CVE-2026-64117, CVE-2026-64118, CVE-2026-64119, CVE-2026-64120, CVE-2026-64121, CVE-2026-64122, CVE-2026-64123, CVE-2026-64124, CVE-2026-64125, CVE-2026-64126, CVE-2026-64127, CVE-2026-64128, CVE-2026-64129, CVE-2026-64130, CVE-2026-64131, CVE-2026-64132, CVE-2026-64133, CVE-2026-64134, CVE-2026-64135, CVE-2026-64136, CVE-2026-64137, CVE-2026-64138, CVE-2026-64139, CVE-2026-64140, CVE-2026-64141, CVE-2026-64142, CVE-2026-64143, CVE-2026-64144, CVE-2026-64145, CVE-2026-64146, CVE-2026-64147, CVE-2026-64148, CVE-2026-64149, CVE-2026-64150, CVE-2026-64151, CVE-2026-64152, CVE-2026-64153, CVE-2026-64154, CVE-2026-64155, CVE-2026-64156, CVE-2026-64157, CVE-2026-64158, CVE-2026-64159, CVE-2026-64160, CVE-2026-64161, CVE-2026-64162, CVE-2026-64163, CVE-2026-64164, CVE-2026-64165, CVE-2026-64166, CVE-2026-64167, CVE-2026-64168, CVE-2026-64169, CVE-2026-64170, CVE-2026-64171, CVE-2026-64172, CVE-2026-64173, CVE-2026-64174, CVE-2026-64175, CVE-2026-64176, CVE-2026-64177, CVE-2026-64178, CVE-2026-64179, CVE-2026-64180, CVE-2026-64181, CVE-2026-64182, CVE-2026-64183, CVE-2026-64184, CVE-2026-64185, CVE-2026-64186, CVE-2026-64208, CVE-2026-64209, CVE-2026-64210, CVE-2026-64211, CVE-2026-64212, CVE-2026-64213, CVE-2026-64214, CVE-2026-64215, CVE-2026-64216, CVE-2026-64217, CVE-2026-64218, CVE-2026-64219, CVE-2026-64220, CVE-2026-64221, CVE-2026-64222, CVE-2026-64223, CVE-2026-64224, CVE-2026-64225, CVE-2026-64226, CVE-2026-64227, CVE-2026-64228, CVE-2026-64229, CVE-2026-64230, CVE-2026-64231, CVE-2026-64232, CVE-2026-64233, CVE-2026-64234, CVE-2026-64235, CVE-2026-64236, CVE-2026-64237, CVE-2026-64238, CVE-2026-64239, CVE-2026-64240, CVE-2026-64241, CVE-2026-64242, CVE-2026-64243, CVE-2026-64515, CVE-2026-64516, CVE-2026-64517, CVE-2026-64518, CVE-2026-64519, CVE-2026-64520, CVE-2026-64521, CVE-2026-64522, CVE-2026-64523, CVE-2026-64524, CVE-2026-64525, CVE-2026-64526, CVE-2026-64527, CVE-2026-64528)
ubuntu.comJul 28, 2026extracted
USN-8603-1: Linux kernel (Azure) vulnerabilities
It was discovered that some AMD processors did not properly clear data in the floating point divider unit during speculative execution. A local attacker could use this to expose sensitive information. (CVE-2025-54505) It was discovered that some AMD Zen 2 processors did not properly isolate shared resources in the operation cache. A local attacker could possibly use this issue to corrupt instructions executed at a higher privilege level, resulting in privilege escalation. (CVE-2025-54518) 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: - x86 platform drivers; - PSP security protocol; - ARM32 architecture; - ARM64 architecture; - MIPS architecture; - PowerPC architecture; - RISC-V architecture; - S390 architecture; - User-Mode Linux (UML); - x86 architecture; - Block layer subsystem; - Cryptographic API; - Intel NPU Driver; - Compute Acceleration Framework; - ACPI drivers; - Auxiliary display drivers; - Drivers core; - DRBD Distributed Replicated Block Device drivers; - Rados block device (RBD) driver; - Ublk userspace block driver; - Compressed RAM block device driver; - Bluetooth drivers; - Bus devices; - Character device driver; - TPM device driver; - Clock framework and drivers; - CPU frequency scaling framework; - Hardware crypto device drivers; - Buffer Sharing and Synchronization framework; - DPLL subsystem; - EDAC drivers; - Arm Firmware Framework for ARMv8-A(FFA); - EFI core; - FWCTL subsystem; - GPIO subsystem; - GPU drivers; - Greybus drivers; - HID subsystem; - Microsoft Hyper-V drivers; - Hardware monitoring drivers; - I2C subsystem; - I3C subsystem; - IIO ADC drivers; - IIO subsystem; - InfiniBand drivers; - Input Device core drivers; - IOMMU subsystem; - LED subsystem; - Mailbox framework; - Multiple devices driver; - Media drivers; - NVIDIA Tegra memory controller driver; - IBM Advanced System Management driver; - MTD block device drivers; - Network drivers; - Ethernet bonding driver; - Mellanox network drivers; - Microsoft Azure Network Adapter (MANA) driver; - STMicroelectronics network drivers; - Texas Instruments network drivers; - MediaTek network drivers; - NTB driver; - NVME drivers; - Device tree and open firmware driver; - Parport drivers; - PCI subsystem; - Pin controllers subsystem; - Chrome hardware platform drivers; - ACPI WMI driver; - Generic PM domains; - MediaTek PM domains; - Power supply drivers; - Remote Processor subsystem; - MPAM driver; - Amlogic Meson reset controller drivers; - S/390 drivers; - SCSI subsystem; - NVIDIA Tegra Control Backbone (CBB) driver; - SPI subsystem; - Greybus lights staging drivers; - Media staging drivers; - Realtek RTL8723BS SDIO drivers; - SM750 framebuffer staging driver; - TCM subsystem; - Thermal drivers; - Thunderbolt and USB4 drivers; - TTY drivers; - Userspace I/O drivers; - USB Device Class drivers; - ULPI bus; - DesignWare USB2 driver; - USB Gadget drivers; - USB Dual Role (OTG-ready) Controller drivers; - USB Serial drivers; - USB Type-C support driver; - USB Type-C Port Controller Manager driver; - TI TPS6598x USB Power Delivery controller driver; - USB Type-C Connector System Software Interface driver; - USB over IP driver; - vDPA drivers; - VFIO drivers; - Framebuffer layer; - TSM AMD SEV Guest driver; - Xen hypervisor drivers; - 9P distributed file system; - File systems infrastructure; - AFS file system; - BTRFS file system; - Ceph distributed file system; - EROFS file system; - Ext4 file system; - F2FS file system; - FUSE (File system in Userspace); - GFS2 file system; - HFS+ file system; - HugeTLB file system; - Journaling layer for block devices (JBD2); - Network file systems library; - Network file system (NFS) server daemon; - NILFS2 file system; - File system notification infrastructure; - NTFS3 file system; - OCFS2 file system; - Overlay file system; - Diskquota system; - SMB network file system; - Tracing file system; - UDF file system; - XFS file system; - DRM TTM subsystem; - Codetag library; - Control group (cgroup); - Kernel CPU control infrastructure; - Memory management; - Tracing infrastructure; - QorIQ DPAA2 FSL-MC bus driver; - Freescale ENETC Ethernet drivers; - Memory Management; - KVM subsystem; - Linked list library; - Netfilter; - padata parallel execution mechanism; - PPP protocol drivers and compressors; - Bluetooth subsystem; - Networking core; - Network shaper API; - Network traffic control; - TCP network protocol; - XFRM subsystem; - User-space API (UAPI); - io_uring subsystem; - IPC subsystem; - Audit subsystem; - BPF subsystem; - DMA mapping infrastructure; - Kernel exit() syscall; - Kernel fork() syscall; - Kernel futex primitives; - IRQ subsystem; - Kexec HandOver (KHO); - Locking primitives; - Padata parallel execution mechanism; - Scheduler infrastructure; - Timer subsystem; - Cryptographic library; - Scatterlist API; - Heterogeneous memory management; - KProbes tracing; - KASAN memory debugging framework; - 802.1Q VLAN protocol; - B.A.T.M.A.N. meshing protocol; - Ethernet bridge; - CAIF protocol; - CAN network layer; - Ceph Core library; - Distributed Switch Architecture; - Ethtool driver; - Handshake API; - HSR network protocol; - IPv4 networking; - IPv6 networking; - IUCV driver; - L2TP protocol; - MAC80211 subsystem; - Multipath TCP; - NFC subsystem; - Open vSwitch; - Packet sockets; - Phonet protocol; - Qualcomm IPC Router (QRTR); - RDS protocol; - RxRPC session sockets; - SCTP protocol; - SMC sockets; - Stream parser; - TIPC protocol; - TLS protocol; - Unix domain sockets; - VMware vSockets driver; - Wireless networking; - Integrity Measurement Architecture(IMA) framework; - Key management; - Landlock security; - Linux Security Modules (LSM) Framework; - SELinux security module; - ALSA framework; - Generic PCM loopback sound driver; - FireWire sound drivers; - HD-audio driver; - AudioScience HPI driver; - Creative Sound Blaster X-Fi driver; - FourSemi audio codecs; - Texas InstrumentS Audio (ASoC/HDA) drivers; - QCOM ASoC drivers; - Renesas ASoC drivers; - SOF drivers; - STI ASoC drivers; - USB sound devices; - Objtool; (CVE-2026-31532, CVE-2026-31574, CVE-2026-31575, CVE-2026-31576, CVE-2026-31577, CVE-2026-31578, CVE-2026-31579, CVE-2026-31580, CVE-2026-31581, CVE-2026-31582, CVE-2026-31583, CVE-2026-31584, CVE-2026-31585, CVE-2026-31586, CVE-2026-31587, CVE-2026-31588, CVE-2026-31589, CVE-2026-31590, CVE-2026-31591, CVE-2026-31592, CVE-2026-31593, CVE-2026-31594, CVE-2026-31595, CVE-2026-31596, CVE-2026-31597, CVE-2026-31598, CVE-2026-31599, CVE-2026-31600, CVE-2026-31601, CVE-2026-31602, CVE-2026-31603, CVE-2026-31604, CVE-2026-31605, CVE-2026-31606, CVE-2026-31607, CVE-2026-31608, CVE-2026-31609, CVE-2026-31610, CVE-2026-31611, CVE-2026-31612, CVE-2026-31613, CVE-2026-31614, CVE-2026-31615, CVE-2026-31616, CVE-2026-31617, CVE-2026-31618, CVE-2026-31619, CVE-2026-31620, CVE-2026-31621, CVE-2026-31622, CVE-2026-31623, CVE-2026-31624, CVE-2026-31625, CVE-2026-31626, CVE-2026-31627, CVE-2026-31628, CVE-2026-31629, CVE-2026-31686, CVE-2026-31694, CVE-2026-31696, CVE-2026-31697, CVE-2026-31698, CVE-2026-31699, CVE-2026-31700, CVE-2026-31701, CVE-2026-31702, CVE-2026-31703, CVE-2026-31704, CVE-2026-31705, CVE-2026-31706, CVE-2026-31707, CVE-2026-31708, CVE-2026-31709, CVE-2026-31710, CVE-2026-31711, CVE-2026-31712, CVE-2026-31713, CVE-2026-31714, CVE-2026-31715, CVE-2026-31716, CVE-2026-31717, CVE-2026-31718, CVE-2026-31719, CVE-2026-43058, CVE-2026-43071, CVE-2026-43072, CVE-2026-43073, CVE-2026-43348, CVE-2026-43349, CVE-2026-43350, CVE-2026-43490, CVE-2026-43491, CVE-2026-43492, CVE-2026-43493, CVE-2026-43495, CVE-2026-43496, CVE-2026-43497, CVE-2026-43498, CVE-2026-43499, CVE-2026-43501, CVE-2026-43502, CVE-2026-45834, CVE-2026-45835, CVE-2026-45836, CVE-2026-45837, CVE-2026-45838, CVE-2026-45839, CVE-2026-45840, CVE-2026-45841, CVE-2026-45842, CVE-2026-45843, CVE-2026-45844, CVE-2026-45845, CVE-2026-45846, CVE-2026-45986, CVE-2026-45987, CVE-2026-45988, CVE-2026-45989, CVE-2026-45990, CVE-2026-45991, CVE-2026-45994, CVE-2026-45995, CVE-2026-45996, CVE-2026-45997, CVE-2026-45999, CVE-2026-46001, CVE-2026-46002, CVE-2026-46003, CVE-2026-46004, CVE-2026-46005, CVE-2026-46006, CVE-2026-46007, CVE-2026-46008, CVE-2026-46009, CVE-2026-46010, CVE-2026-46011, CVE-2026-46012, CVE-2026-46013, CVE-2026-46014, CVE-2026-46015, CVE-2026-46016, CVE-2026-46018, CVE-2026-46019, CVE-2026-46020, CVE-2026-46021, CVE-2026-46022, CVE-2026-46023, CVE-2026-46024, CVE-2026-46025, CVE-2026-46026, CVE-2026-46027, CVE-2026-46028, CVE-2026-46029, CVE-2026-46030, CVE-2026-46031, CVE-2026-46032, CVE-2026-46033, CVE-2026-46034, CVE-2026-46035, CVE-2026-46036, CVE-2026-46037, CVE-2026-46038, CVE-2026-46039, CVE-2026-46040, CVE-2026-46041, CVE-2026-46042, CVE-2026-46043, CVE-2026-46044, CVE-2026-46045, CVE-2026-46046, CVE-2026-46047, CVE-2026-46049, CVE-2026-46050, CVE-2026-46051, CVE-2026-46052, CVE-2026-46053, CVE-2026-46054, CVE-2026-46056, CVE-2026-46057, CVE-2026-46058, CVE-2026-46059, CVE-2026-46060, CVE-2026-46061, CVE-2026-46062, CVE-2026-46063, CVE-2026-46064, CVE-2026-46065, CVE-2026-46066, CVE-2026-46067, CVE-2026-46068, CVE-2026-46069, CVE-2026-46070, CVE-2026-46071, CVE-2026-46072, CVE-2026-46073, CVE-2026-46074, CVE-2026-46075, CVE-2026-46076, CVE-2026-46077, CVE-2026-46078, CVE-2026-46079, CVE-2026-46080, CVE-2026-46081, CVE-2026-46082, CVE-2026-46083, CVE-2026-46084, CVE-2026-46085, CVE-2026-46086, CVE-2026-46087, CVE-2026-46088, CVE-2026-46089, CVE-2026-46090, CVE-2026-46091, CVE-2026-46092, CVE-2026-46093, CVE-2026-46094, CVE-2026-46095, CVE-2026-46096, CVE-2026-46097, CVE-2026-46098, CVE-2026-46099, CVE-2026-46100, CVE-2026-46101, CVE-2026-46102, CVE-2026-46103, CVE-2026-46104, CVE-2026-46105, CVE-2026-46106, CVE-2026-46107, CVE-2026-46108, CVE-2026-46109, CVE-2026-46110, CVE-2026-46111, CVE-2026-46112, CVE-2026-46113, CVE-2026-46114, CVE-2026-46115, CVE-2026-46116, CVE-2026-46117, CVE-2026-46118, CVE-2026-46119, CVE-2026-46120, CVE-2026-46121, CVE-2026-46122, CVE-2026-46123, CVE-2026-46124, CVE-2026-46125, CVE-2026-46126, CVE-2026-46127, CVE-2026-46128, CVE-2026-46129, CVE-2026-46130, CVE-2026-46131, CVE-2026-46132, CVE-2026-46133, CVE-2026-46134, CVE-2026-46135, CVE-2026-46136, CVE-2026-46137, CVE-2026-46138, CVE-2026-46139, CVE-2026-46140, CVE-2026-46141, CVE-2026-46142, CVE-2026-46143, CVE-2026-46144, CVE-2026-46145, CVE-2026-46146, CVE-2026-46147, CVE-2026-46148, CVE-2026-46149, CVE-2026-46150, CVE-2026-46151, CVE-2026-46152, CVE-2026-46153, CVE-2026-46154, CVE-2026-46155, CVE-2026-46156, CVE-2026-46157, CVE-2026-46158, CVE-2026-46159, CVE-2026-46160, CVE-2026-46161, CVE-2026-46162, CVE-2026-46163, CVE-2026-46164, CVE-2026-46165, CVE-2026-46166, CVE-2026-46167, CVE-2026-46168, CVE-2026-46169, CVE-2026-46170, CVE-2026-46171, CVE-2026-46172, CVE-2026-46173, CVE-2026-46174, CVE-2026-46175, CVE-2026-46176, CVE-2026-46177, CVE-2026-46178, CVE-2026-46179, CVE-2026-46180, CVE-2026-46181, CVE-2026-46182, CVE-2026-46183, CVE-2026-46184, CVE-2026-46185, CVE-2026-46186, CVE-2026-46187, CVE-2026-46188, CVE-2026-46189, CVE-2026-46190, CVE-2026-46191, CVE-2026-46192, CVE-2026-46193, CVE-2026-46194, CVE-2026-46195, CVE-2026-46196, CVE-2026-46197, CVE-2026-46198, CVE-2026-46199, CVE-2026-46200, CVE-2026-46201, CVE-2026-46202, CVE-2026-46203, CVE-2026-46204, CVE-2026-46205, CVE-2026-46206, CVE-2026-46207, CVE-2026-46208, CVE-2026-46209, CVE-2026-46210, CVE-2026-46211, CVE-2026-46212, CVE-2026-46213, CVE-2026-46214, CVE-2026-46215, CVE-2026-46216, CVE-2026-46218, CVE-2026-46219, CVE-2026-46220, CVE-2026-46221, CVE-2026-46222, CVE-2026-46223, CVE-2026-46224, CVE-2026-46225, CVE-2026-46226, CVE-2026-46227, CVE-2026-46228, CVE-2026-46229, CVE-2026-46230, CVE-2026-46231, CVE-2026-46232, CVE-2026-46233, CVE-2026-46234, CVE-2026-46235, CVE-2026-46236, CVE-2026-46238, CVE-2026-46239, CVE-2026-46240, CVE-2026-46241, CVE-2026-46242, CVE-2026-46243, CVE-2026-46244, CVE-2026-46273, CVE-2026-46274, CVE-2026-46275, CVE-2026-46276, CVE-2026-46277, CVE-2026-46278, CVE-2026-46279, CVE-2026-46280, CVE-2026-46281, CVE-2026-46282, CVE-2026-46283, CVE-2026-46284, CVE-2026-46285, CVE-2026-46286, CVE-2026-46287, CVE-2026-46288, CVE-2026-46289, CVE-2026-46290, CVE-2026-46291, CVE-2026-46292, CVE-2026-46293, CVE-2026-46294, CVE-2026-46295, CVE-2026-46296, CVE-2026-46297, CVE-2026-46298, CVE-2026-46299, CVE-2026-46301, CVE-2026-46302, CVE-2026-46303, CVE-2026-46304, CVE-2026-46305, CVE-2026-46306, CVE-2026-46307, CVE-2026-46308, CVE-2026-46309, CVE-2026-46310, CVE-2026-46311, CVE-2026-46312, CVE-2026-46313, CVE-2026-46314, CVE-2026-46315, CVE-2026-46316, CVE-2026-46317, CVE-2026-46318, CVE-2026-46319, CVE-2026-46320, CVE-2026-46321, CVE-2026-46322, CVE-2026-46324, CVE-2026-46332, CVE-2026-52904, CVE-2026-52905, CVE-2026-52906, CVE-2026-52907, CVE-2026-52911, CVE-2026-52912, CVE-2026-52913, CVE-2026-52914, CVE-2026-52915, CVE-2026-52916, CVE-2026-52918, CVE-2026-52919, CVE-2026-52920, CVE-2026-52921, CVE-2026-52922, CVE-2026-52923, CVE-2026-52925, CVE-2026-52926, CVE-2026-52927, CVE-2026-52928, CVE-2026-52931, CVE-2026-52932, CVE-2026-52933, CVE-2026-52934, CVE-2026-52936, CVE-2026-52937, CVE-2026-52941, CVE-2026-52943, CVE-2026-52944, CVE-2026-52949, CVE-2026-52950, CVE-2026-52951, CVE-2026-52952, CVE-2026-52953, CVE-2026-52954, CVE-2026-52955, CVE-2026-52956, CVE-2026-52957, CVE-2026-52958, CVE-2026-52959, CVE-2026-52960, CVE-2026-52961, CVE-2026-52962, CVE-2026-52963, CVE-2026-52964, CVE-2026-52965, CVE-2026-52967, CVE-2026-52968, CVE-2026-52969, CVE-2026-52970, CVE-2026-52971, CVE-2026-52973, CVE-2026-52974, CVE-2026-52975, CVE-2026-52976, CVE-2026-52977, CVE-2026-52978, CVE-2026-52979, CVE-2026-52980, CVE-2026-52981, CVE-2026-52982, CVE-2026-52983, CVE-2026-52984, CVE-2026-52985, CVE-2026-52986, CVE-2026-52987, CVE-2026-52988, CVE-2026-52989, CVE-2026-52990, CVE-2026-52991, CVE-2026-52992, CVE-2026-52993, CVE-2026-52994, CVE-2026-52995, CVE-2026-52996, CVE-2026-52997, CVE-2026-52998, CVE-2026-52999, CVE-2026-53000, CVE-2026-53001, CVE-2026-53002, CVE-2026-53003, CVE-2026-53004, CVE-2026-53005, CVE-2026-53006, CVE-2026-53007, CVE-2026-53008, CVE-2026-53009, CVE-2026-53010, CVE-2026-53011, CVE-2026-53012, CVE-2026-53013, CVE-2026-53014, CVE-2026-53015, CVE-2026-53016, CVE-2026-53017, CVE-2026-53018, CVE-2026-53019, CVE-2026-53020, CVE-2026-53021, CVE-2026-53022, CVE-2026-53023, CVE-2026-53024, CVE-2026-53025, CVE-2026-53026, CVE-2026-53027, CVE-2026-53028, CVE-2026-53029, CVE-2026-53030, CVE-2026-53031, CVE-2026-53032, CVE-2026-53033, CVE-2026-53034, CVE-2026-53035, CVE-2026-53036, CVE-2026-53037, CVE-2026-53038, CVE-2026-53039, CVE-2026-53040, CVE-2026-53041, CVE-2026-53042, CVE-2026-53043, CVE-2026-53044, CVE-2026-53045, CVE-2026-53046, CVE-2026-53047, CVE-2026-53048, CVE-2026-53049, CVE-2026-53050, CVE-2026-53051, CVE-2026-53052, CVE-2026-53053, CVE-2026-53054, CVE-2026-53055, CVE-2026-53056, CVE-2026-53057, CVE-2026-53058, CVE-2026-53059, CVE-2026-53060, CVE-2026-53061, CVE-2026-53062, CVE-2026-53063, CVE-2026-53064, CVE-2026-53065, CVE-2026-53066, CVE-2026-53067, CVE-2026-53068, CVE-2026-53069, CVE-2026-53070, CVE-2026-53071, CVE-2026-53072, CVE-2026-53073, CVE-2026-53074, CVE-2026-53075, CVE-2026-53076, CVE-2026-53077, CVE-2026-53078, CVE-2026-53079, CVE-2026-53080, CVE-2026-53081, CVE-2026-53082, CVE-2026-53083, CVE-2026-53084, CVE-2026-53085, CVE-2026-53086, CVE-2026-53087, CVE-2026-53088, CVE-2026-53089, CVE-2026-53090, CVE-2026-53091, CVE-2026-53092, CVE-2026-53093, CVE-2026-53094, CVE-2026-53095, CVE-2026-53096, CVE-2026-53097, CVE-2026-53098, CVE-2026-53099, CVE-2026-53100, CVE-2026-53101, CVE-2026-53102, CVE-2026-53103, CVE-2026-53104, CVE-2026-53105, CVE-2026-53106, CVE-2026-53107, CVE-2026-53108, CVE-2026-53109, CVE-2026-53110, CVE-2026-53111, CVE-2026-53112, CVE-2026-53113, CVE-2026-53114, CVE-2026-53115, CVE-2026-53116, CVE-2026-53117, CVE-2026-53118, CVE-2026-53119, CVE-2026-53120, CVE-2026-53121, CVE-2026-53122, CVE-2026-53123, CVE-2026-53124, CVE-2026-53125, CVE-2026-53126, CVE-2026-53127, CVE-2026-53128, CVE-2026-53129, CVE-2026-53130, CVE-2026-53174, CVE-2026-53277, CVE-2026-53278, CVE-2026-53279, CVE-2026-53280, CVE-2026-53281, CVE-2026-53282, CVE-2026-53283, CVE-2026-53284, CVE-2026-53285, CVE-2026-53286, CVE-2026-53287, CVE-2026-53288, CVE-2026-53289, CVE-2026-53290, CVE-2026-53291, CVE-2026-53292, CVE-2026-53293, CVE-2026-53294, CVE-2026-53295, CVE-2026-53296, CVE-2026-53297, CVE-2026-53298, CVE-2026-53299, CVE-2026-53300, CVE-2026-53301, CVE-2026-53302, CVE-2026-53303, CVE-2026-53304, CVE-2026-53305, CVE-2026-53306, CVE-2026-53307, CVE-2026-53308, CVE-2026-53309, CVE-2026-53310, CVE-2026-53311, CVE-2026-53312, CVE-2026-53313, CVE-2026-53314, CVE-2026-53315, CVE-2026-53316, CVE-2026-53317, CVE-2026-53318, CVE-2026-53319, CVE-2026-53320, CVE-2026-53321, CVE-2026-53322, CVE-2026-53323, CVE-2026-53324, CVE-2026-53357, CVE-2026-53358, CVE-2026-53360, CVE-2026-53364, CVE-2026-53365, CVE-2026-53367, CVE-2026-53368, CVE-2026-53369, CVE-2026-53370, CVE-2026-53371, CVE-2026-53372, CVE-2026-53373, CVE-2026-53374, CVE-2026-53375, CVE-2026-53376, CVE-2026-53377, CVE-2026-53378, CVE-2026-53379, CVE-2026-53380, CVE-2026-63837, CVE-2026-63838, CVE-2026-63839, CVE-2026-63840, CVE-2026-63841, CVE-2026-63842, CVE-2026-63843, CVE-2026-63844, CVE-2026-63845, CVE-2026-63846, CVE-2026-63847, CVE-2026-63848, CVE-2026-63849, CVE-2026-63850, CVE-2026-63851, CVE-2026-63852, CVE-2026-63853, CVE-2026-63854, CVE-2026-63855, CVE-2026-63856, CVE-2026-63857, CVE-2026-63858, CVE-2026-63859, CVE-2026-63860, CVE-2026-63861, CVE-2026-63862, CVE-2026-63863, CVE-2026-63864, CVE-2026-63865, CVE-2026-63866, CVE-2026-63875, CVE-2026-63876, CVE-2026-63877, CVE-2026-63878, CVE-2026-63879, CVE-2026-63880, CVE-2026-63881, CVE-2026-63882, CVE-2026-63883, CVE-2026-63884, CVE-2026-63886, CVE-2026-63887, CVE-2026-63888, CVE-2026-63889, CVE-2026-63890, CVE-2026-63891, CVE-2026-63892, CVE-2026-63893, CVE-2026-63894, CVE-2026-63895, CVE-2026-63896, CVE-2026-63897, CVE-2026-63898, CVE-2026-63899, CVE-2026-63900, CVE-2026-63901, CVE-2026-63902, CVE-2026-63903, CVE-2026-63904, CVE-2026-63905, CVE-2026-63906, CVE-2026-63907, CVE-2026-63908, CVE-2026-63910, CVE-2026-63911, CVE-2026-63912, CVE-2026-63913, CVE-2026-63914, CVE-2026-63915, CVE-2026-63916, CVE-2026-63917, CVE-2026-63918, CVE-2026-63919, CVE-2026-63920, CVE-2026-63921, CVE-2026-63922, CVE-2026-63923, CVE-2026-63924, CVE-2026-63925, CVE-2026-63926, CVE-2026-63927, CVE-2026-63928, CVE-2026-63929, CVE-2026-63930, CVE-2026-63931, CVE-2026-63932, CVE-2026-63933, CVE-2026-63934, CVE-2026-63935, CVE-2026-63936, CVE-2026-63937, CVE-2026-63938, CVE-2026-63939, CVE-2026-63940, CVE-2026-63941, CVE-2026-63942, CVE-2026-63943, CVE-2026-63944, CVE-2026-63945, CVE-2026-63946, CVE-2026-63947, CVE-2026-63948, CVE-2026-63949, CVE-2026-63950, CVE-2026-63951, CVE-2026-63952, CVE-2026-63953, CVE-2026-63954, CVE-2026-63955, CVE-2026-63956, CVE-2026-63957, CVE-2026-63958, CVE-2026-63959, CVE-2026-63960, CVE-2026-63961, CVE-2026-63962, CVE-2026-63963, CVE-2026-63964, CVE-2026-63965, CVE-2026-63966, CVE-2026-63967, CVE-2026-63968, CVE-2026-63969, CVE-2026-63970, CVE-2026-63971, CVE-2026-63972, CVE-2026-63973, CVE-2026-63974, CVE-2026-63975, CVE-2026-63976, CVE-2026-63977, CVE-2026-63978, CVE-2026-63979, CVE-2026-63980, CVE-2026-63981, CVE-2026-63982, CVE-2026-63983, CVE-2026-63984, CVE-2026-63985, CVE-2026-63986, CVE-2026-63987, CVE-2026-63988, CVE-2026-63989, CVE-2026-63990, CVE-2026-63991, CVE-2026-63992, CVE-2026-63993, CVE-2026-63994, CVE-2026-63995, CVE-2026-63996, CVE-2026-63997, CVE-2026-63998, CVE-2026-63999, CVE-2026-64000, CVE-2026-64001, CVE-2026-64002, CVE-2026-64003, CVE-2026-64004, CVE-2026-64005, CVE-2026-64006, CVE-2026-64007, CVE-2026-64008, CVE-2026-64009, CVE-2026-64010, CVE-2026-64011, CVE-2026-64012, CVE-2026-64013, CVE-2026-64014, CVE-2026-64015, CVE-2026-64017, CVE-2026-64018, CVE-2026-64019, CVE-2026-64020, CVE-2026-64021, CVE-2026-64022, CVE-2026-64023, CVE-2026-64024, CVE-2026-64025, CVE-2026-64026, CVE-2026-64027, CVE-2026-64029, CVE-2026-64030, CVE-2026-64031, CVE-2026-64032, CVE-2026-64033, CVE-2026-64034, CVE-2026-64035, CVE-2026-64036, CVE-2026-64037, CVE-2026-64038, CVE-2026-64039, CVE-2026-64040, CVE-2026-64041, CVE-2026-64042, CVE-2026-64043, CVE-2026-64044, CVE-2026-64045, CVE-2026-64046, CVE-2026-64047, CVE-2026-64048, CVE-2026-64049, CVE-2026-64050, CVE-2026-64051, CVE-2026-64052, CVE-2026-64053, CVE-2026-64054, CVE-2026-64055, CVE-2026-64056, CVE-2026-64057, CVE-2026-64058, CVE-2026-64059, CVE-2026-64060, CVE-2026-64061, CVE-2026-64062, CVE-2026-64063, CVE-2026-64064, CVE-2026-64065, CVE-2026-64066, CVE-2026-64067, CVE-2026-64068, CVE-2026-64069, CVE-2026-64070, CVE-2026-64071, CVE-2026-64072, CVE-2026-64073, CVE-2026-64074, CVE-2026-64075, CVE-2026-64076, CVE-2026-64077, CVE-2026-64078, CVE-2026-64079, CVE-2026-64080, CVE-2026-64081, CVE-2026-64082, CVE-2026-64083, CVE-2026-64084, CVE-2026-64085, CVE-2026-64086, CVE-2026-64087, CVE-2026-64088, CVE-2026-64089, CVE-2026-64090, CVE-2026-64091, CVE-2026-64093, CVE-2026-64094, CVE-2026-64095, CVE-2026-64096, CVE-2026-64097, CVE-2026-64098, CVE-2026-64099, CVE-2026-64100, CVE-2026-64101, CVE-2026-64102, CVE-2026-64103, CVE-2026-64104, CVE-2026-64105, CVE-2026-64106, CVE-2026-64107, CVE-2026-64108, CVE-2026-64109, CVE-2026-64110, CVE-2026-64111, CVE-2026-64112, CVE-2026-64113, CVE-2026-64114, CVE-2026-64115, CVE-2026-64116, CVE-2026-64117, CVE-2026-64118, CVE-2026-64119, CVE-2026-64120, CVE-2026-64121, CVE-2026-64122, CVE-2026-64123, CVE-2026-64124, CVE-2026-64125, CVE-2026-64126, CVE-2026-64127, CVE-2026-64128, CVE-2026-64129, CVE-2026-64130, CVE-2026-64131, CVE-2026-64132, CVE-2026-64133, CVE-2026-64134, CVE-2026-64135, CVE-2026-64136, CVE-2026-64137, CVE-2026-64138, CVE-2026-64140, CVE-2026-64141, CVE-2026-64142, CVE-2026-64143, CVE-2026-64144, CVE-2026-64145, CVE-2026-64146, CVE-2026-64147, CVE-2026-64148, CVE-2026-64149, CVE-2026-64150, CVE-2026-64151, CVE-2026-64152, CVE-2026-64153, CVE-2026-64154, CVE-2026-64155, CVE-2026-64156, CVE-2026-64157, CVE-2026-64158, CVE-2026-64159, CVE-2026-64160, CVE-2026-64161, CVE-2026-64162, CVE-2026-64163, CVE-2026-64164, CVE-2026-64165, CVE-2026-64166, CVE-2026-64167, CVE-2026-64168, CVE-2026-64169, CVE-2026-64170, CVE-2026-64171, CVE-2026-64172, CVE-2026-64173, CVE-2026-64174, CVE-2026-64175, CVE-2026-64176, CVE-2026-64177, CVE-2026-64178, CVE-2026-64179, CVE-2026-64180, CVE-2026-64181, CVE-2026-64182, CVE-2026-64183, CVE-2026-64184, CVE-2026-64185, CVE-2026-64186)
ubuntu.comJul 24, 2026extracted
USN-8593-1: Linux kernel vulnerabilities
It was discovered that some AMD Zen 2 processors did not properly isolate shared resources in the operation cache. A local attacker could possibly use this issue to corrupt instructions executed at a higher privilege level, resulting in privilege escalation. (CVE-2025-54518) 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: - x86 platform drivers; - PSP security protocol; - ARM32 architecture; - ARM64 architecture; - MIPS architecture; - PowerPC architecture; - RISC-V architecture; - S390 architecture; - User-Mode Linux (UML); - x86 architecture; - Block layer subsystem; - Cryptographic API; - Intel NPU Driver; - Compute Acceleration Framework; - ACPI drivers; - Auxiliary display drivers; - Drivers core; - DRBD Distributed Replicated Block Device drivers; - Rados block device (RBD) driver; - Ublk userspace block driver; - Compressed RAM block device driver; - Bluetooth drivers; - Bus devices; - Character device driver; - Clock framework and drivers; - CPU frequency scaling framework; - Hardware crypto device drivers; - Buffer Sharing and Synchronization framework; - DPLL subsystem; - EDAC drivers; - Arm Firmware Framework for ARMv8-A(FFA); - EFI core; - FWCTL subsystem; - GPIO subsystem; - GPU drivers; - HID subsystem; - Hardware monitoring drivers; - I2C subsystem; - I3C subsystem; - IIO ADC drivers; - IIO subsystem; - InfiniBand drivers; - Input Device core drivers; - IOMMU subsystem; - Mailbox framework; - Multiple devices driver; - Media drivers; - NVIDIA Tegra memory controller driver; - MTD block device drivers; - Network drivers; - Ethernet bonding driver; - Mellanox network drivers; - Microsoft Azure Network Adapter (MANA) driver; - STMicroelectronics network drivers; - Texas Instruments network drivers; - MediaTek network drivers; - NVME drivers; - Parport drivers; - PCI subsystem; - Pin controllers subsystem; - Chrome hardware platform drivers; - ACPI WMI driver; - Generic PM domains; - MediaTek PM domains; - Power supply drivers; - MPAM driver; - Amlogic Meson reset controller drivers; - S/390 drivers; - SCSI subsystem; - NVIDIA Tegra Control Backbone (CBB) driver; - SPI subsystem; - Greybus lights staging drivers; - Media staging drivers; - Realtek RTL8723BS SDIO drivers; - TCM subsystem; - Thunderbolt and USB4 drivers; - TTY drivers; - Userspace I/O drivers; - USB Device Class drivers; - ULPI bus; - DesignWare USB2 driver; - USB Gadget drivers; - USB Dual Role (OTG-ready) Controller drivers; - USB Serial drivers; - USB Type-C support driver; - USB Type-C Port Controller Manager driver; - TI TPS6598x USB Power Delivery controller driver; - USB Type-C Connector System Software Interface driver; - USB over IP driver; - vDPA drivers; - VFIO drivers; - Framebuffer layer; - TSM AMD SEV Guest driver; - Xen hypervisor drivers; - 9P distributed file system; - File systems infrastructure; - AFS file system; - BTRFS file system; - Ceph distributed file system; - EROFS file system; - F2FS file system; - FUSE (File system in Userspace); - GFS2 file system; - HFS+ file system; - HugeTLB file system; - Network file systems library; - Network file system (NFS) server daemon; - NILFS2 file system; - File system notification infrastructure; - NTFS3 file system; - OCFS2 file system; - Overlay file system; - Diskquota system; - SMB network file system; - Tracing file system; - UDF file system; - DRM TTM subsystem; - Control group (cgroup); - Kernel CPU control infrastructure; - Tracing infrastructure; - QorIQ DPAA2 FSL-MC bus driver; - Freescale ENETC Ethernet drivers; - Memory management; - Memory Management; - Linked list library; - Netfilter; - padata parallel execution mechanism; - PPP protocol drivers and compressors; - Bluetooth subsystem; - Networking core; - Network shaper API; - Network traffic control; - TCP network protocol; - XFRM subsystem; - io_uring subsystem; - IPC subsystem; - Audit subsystem; - BPF subsystem; - DMA mapping infrastructure; - Kernel exit() syscall; - Kernel fork() syscall; - Kernel futex primitives; - IRQ subsystem; - Kexec HandOver (KHO); - Padata parallel execution mechanism; - Scheduler infrastructure; - Cryptographic library; - KProbes tracing; - 802.1Q VLAN protocol; - B.A.T.M.A.N. meshing protocol; - Ethernet bridge; - Ceph Core library; - Distributed Switch Architecture; - Ethtool driver; - Handshake API; - HSR network protocol; - IPv4 networking; - IPv6 networking; - IUCV driver; - L2TP protocol; - MAC80211 subsystem; - Multipath TCP; - NFC subsystem; - Open vSwitch; - Phonet protocol; - RDS protocol; - RxRPC session sockets; - SCTP protocol; - SMC sockets; - TIPC protocol; - TLS protocol; - Unix domain sockets; - VMware vSockets driver; - Wireless networking; - Integrity Measurement Architecture(IMA) framework; - Key management; - Linux Security Modules (LSM) Framework; - SELinux security module; - ALSA framework; - HD-audio driver; - AudioScience HPI driver; - FourSemi audio codecs; - Texas InstrumentS Audio (ASoC/HDA) drivers; - QCOM ASoC drivers; - Renesas ASoC drivers; - SOF drivers; - STI ASoC drivers; - USB sound devices; - KVM subsystem; (CVE-2026-43490, CVE-2026-43492, CVE-2026-43495, CVE-2026-43496, CVE-2026-43497, CVE-2026-43498, CVE-2026-43502, CVE-2026-45834, CVE-2026-45835, CVE-2026-45836, CVE-2026-45837, CVE-2026-45838, CVE-2026-45839, CVE-2026-45840, CVE-2026-45841, CVE-2026-45842, CVE-2026-45843, CVE-2026-45844, CVE-2026-45845, CVE-2026-45846, CVE-2026-46104, CVE-2026-46105, CVE-2026-46106, CVE-2026-46107, CVE-2026-46108, CVE-2026-46109, CVE-2026-46110, CVE-2026-46111, CVE-2026-46112, CVE-2026-46113, CVE-2026-46114, CVE-2026-46116, CVE-2026-46117, CVE-2026-46118, CVE-2026-46120, CVE-2026-46121, CVE-2026-46122, CVE-2026-46123, CVE-2026-46124, CVE-2026-46125, CVE-2026-46126, CVE-2026-46127, CVE-2026-46128, CVE-2026-46129, CVE-2026-46130, CVE-2026-46131, CVE-2026-46132, CVE-2026-46133, CVE-2026-46134, CVE-2026-46136, CVE-2026-46138, CVE-2026-46139, CVE-2026-46140, CVE-2026-46141, CVE-2026-46142, CVE-2026-46143, CVE-2026-46144, CVE-2026-46145, CVE-2026-46146, CVE-2026-46147, CVE-2026-46148, CVE-2026-46149, CVE-2026-46150, CVE-2026-46151, CVE-2026-46152, CVE-2026-46153, CVE-2026-46154, CVE-2026-46156, CVE-2026-46157, CVE-2026-46158, CVE-2026-46159, CVE-2026-46160, CVE-2026-46161, CVE-2026-46162, CVE-2026-46163, CVE-2026-46164, CVE-2026-46165, CVE-2026-46166, CVE-2026-46167, CVE-2026-46168, CVE-2026-46169, CVE-2026-46170, CVE-2026-46171, CVE-2026-46172, CVE-2026-46173, CVE-2026-46174, CVE-2026-46175, CVE-2026-46176, CVE-2026-46177, CVE-2026-46178, CVE-2026-46179, CVE-2026-46180, CVE-2026-46181, CVE-2026-46182, CVE-2026-46183, CVE-2026-46184, CVE-2026-46186, CVE-2026-46187, CVE-2026-46188, CVE-2026-46189, CVE-2026-46190, CVE-2026-46191, CVE-2026-46192, CVE-2026-46193, CVE-2026-46194, CVE-2026-46196, CVE-2026-46197, CVE-2026-46198, CVE-2026-46199, CVE-2026-46200, CVE-2026-46201, CVE-2026-46202, CVE-2026-46203, CVE-2026-46204, CVE-2026-46205, CVE-2026-46206, CVE-2026-46207, CVE-2026-46208, CVE-2026-46209, CVE-2026-46210, CVE-2026-46211, CVE-2026-46212, CVE-2026-46213, CVE-2026-46214, CVE-2026-46215, CVE-2026-46216, CVE-2026-46218, CVE-2026-46219, CVE-2026-46220, CVE-2026-46221, CVE-2026-46222, CVE-2026-46223, CVE-2026-46224, CVE-2026-46225, CVE-2026-46226, CVE-2026-46227, CVE-2026-46228, CVE-2026-46229, CVE-2026-46230, CVE-2026-46231, CVE-2026-46232, CVE-2026-46233, CVE-2026-46234, CVE-2026-46235, CVE-2026-46236, CVE-2026-46238, CVE-2026-46239, CVE-2026-46240, CVE-2026-46241, CVE-2026-46242, CVE-2026-46273, CVE-2026-46274, CVE-2026-46275, CVE-2026-46290, CVE-2026-46291, CVE-2026-46292, CVE-2026-46293, CVE-2026-46294, CVE-2026-46295, CVE-2026-46296, CVE-2026-46297, CVE-2026-46298, CVE-2026-46299, CVE-2026-46301, CVE-2026-46302, CVE-2026-46303, CVE-2026-46304, CVE-2026-46305, CVE-2026-46306, CVE-2026-46307, CVE-2026-46308, CVE-2026-46309, CVE-2026-46310, CVE-2026-46311, CVE-2026-46312, CVE-2026-46313, CVE-2026-46314, CVE-2026-46315, CVE-2026-46317, CVE-2026-46318, CVE-2026-46319, CVE-2026-46320, CVE-2026-46321, CVE-2026-46322, CVE-2026-46324, CVE-2026-52911, CVE-2026-52912, CVE-2026-52913, CVE-2026-52914, CVE-2026-52915, CVE-2026-52916, CVE-2026-52918, CVE-2026-52919, CVE-2026-52920, CVE-2026-52921, CVE-2026-52922, CVE-2026-52923, CVE-2026-52925, CVE-2026-52926, CVE-2026-52927, CVE-2026-52928, CVE-2026-52931, CVE-2026-52932, CVE-2026-52934, CVE-2026-52936, CVE-2026-52937, CVE-2026-52941, CVE-2026-52943, CVE-2026-52944, CVE-2026-52949, CVE-2026-52950, CVE-2026-52951, CVE-2026-52952, CVE-2026-52953, CVE-2026-52954, CVE-2026-52955, CVE-2026-52956, CVE-2026-52957, CVE-2026-52958, CVE-2026-52959, CVE-2026-52960, CVE-2026-52961, CVE-2026-52962, CVE-2026-52963, CVE-2026-52964, CVE-2026-52965, CVE-2026-52967, CVE-2026-52968, CVE-2026-52969, CVE-2026-52970, CVE-2026-52971, CVE-2026-52973, CVE-2026-52974, CVE-2026-52975, CVE-2026-52976, CVE-2026-52977, CVE-2026-52978, CVE-2026-52979, CVE-2026-52980, CVE-2026-52981, CVE-2026-52982, CVE-2026-52983, CVE-2026-52984, CVE-2026-52985, CVE-2026-52986, CVE-2026-52987, CVE-2026-52988, CVE-2026-52989, CVE-2026-52990, CVE-2026-52991, CVE-2026-52992, CVE-2026-52993, CVE-2026-52994, CVE-2026-52995, CVE-2026-52996, CVE-2026-52997, CVE-2026-52998, CVE-2026-52999, CVE-2026-53000, CVE-2026-53001, CVE-2026-53002, CVE-2026-53003, CVE-2026-53004, CVE-2026-53005, CVE-2026-53006, CVE-2026-53007, CVE-2026-53008, CVE-2026-53009, CVE-2026-53010, CVE-2026-53011, CVE-2026-53012, CVE-2026-53013, CVE-2026-53014, CVE-2026-53015, CVE-2026-53016, CVE-2026-53017, CVE-2026-53018, CVE-2026-53019, CVE-2026-53020, CVE-2026-53021, CVE-2026-53022, CVE-2026-53023, CVE-2026-53024, CVE-2026-53025, CVE-2026-53026, CVE-2026-53027, CVE-2026-53028, CVE-2026-53029, CVE-2026-53030, CVE-2026-53031, CVE-2026-53032, CVE-2026-53033, CVE-2026-53034, CVE-2026-53035, CVE-2026-53036, CVE-2026-53037, CVE-2026-53038, CVE-2026-53039, CVE-2026-53040, CVE-2026-53041, CVE-2026-53042, CVE-2026-53043, CVE-2026-53044, CVE-2026-53045, CVE-2026-53046, CVE-2026-53047, CVE-2026-53048, CVE-2026-53049, CVE-2026-53050, CVE-2026-53051, CVE-2026-53052, CVE-2026-53053, CVE-2026-53054, CVE-2026-53055, CVE-2026-53056, CVE-2026-53057, CVE-2026-53058, CVE-2026-53059, CVE-2026-53060, CVE-2026-53061, CVE-2026-53062, CVE-2026-53063, CVE-2026-53064, CVE-2026-53065, CVE-2026-53066, CVE-2026-53067, CVE-2026-53068, CVE-2026-53069, CVE-2026-53070, CVE-2026-53071, CVE-2026-53072, CVE-2026-53073, CVE-2026-53074, CVE-2026-53075, CVE-2026-53076, CVE-2026-53077, CVE-2026-53078, CVE-2026-53079, CVE-2026-53080, CVE-2026-53081, CVE-2026-53082, CVE-2026-53083, CVE-2026-53084, CVE-2026-53085, CVE-2026-53086, CVE-2026-53087, CVE-2026-53088, CVE-2026-53089, CVE-2026-53090, CVE-2026-53091, CVE-2026-53092, CVE-2026-53093, CVE-2026-53094, CVE-2026-53095, CVE-2026-53096, CVE-2026-53097, CVE-2026-53098, CVE-2026-53099, CVE-2026-53100, CVE-2026-53101, CVE-2026-53102, CVE-2026-53103, CVE-2026-53104, CVE-2026-53105, CVE-2026-53106, CVE-2026-53107, CVE-2026-53108, CVE-2026-53109, CVE-2026-53110, CVE-2026-53111, CVE-2026-53112, CVE-2026-53113, CVE-2026-53114, CVE-2026-53115, CVE-2026-53116, CVE-2026-53117, CVE-2026-53118, CVE-2026-53119, CVE-2026-53120, CVE-2026-53121, CVE-2026-53122, CVE-2026-53123, CVE-2026-53124, CVE-2026-53125, CVE-2026-53126, CVE-2026-53127, CVE-2026-53128, CVE-2026-53129, CVE-2026-53130, CVE-2026-53174, CVE-2026-53277, CVE-2026-53278, CVE-2026-53279, CVE-2026-53280, CVE-2026-53281, CVE-2026-53282, CVE-2026-53283, CVE-2026-53284, CVE-2026-53285, CVE-2026-53286, CVE-2026-53287, CVE-2026-53288, CVE-2026-53289, CVE-2026-53290, CVE-2026-53291, CVE-2026-53292, CVE-2026-53293, CVE-2026-53294, CVE-2026-53295, CVE-2026-53296, CVE-2026-53297, CVE-2026-53298, CVE-2026-53299, CVE-2026-53300, CVE-2026-53301, CVE-2026-53302, CVE-2026-53303, CVE-2026-53304, CVE-2026-53305, CVE-2026-53306, CVE-2026-53307, CVE-2026-53308, CVE-2026-53309, CVE-2026-53310, CVE-2026-53311, CVE-2026-53312, CVE-2026-53313, CVE-2026-53314, CVE-2026-53315, CVE-2026-53316, CVE-2026-53317, CVE-2026-53318, CVE-2026-53319, CVE-2026-53320, CVE-2026-53321, CVE-2026-53322, CVE-2026-53323, CVE-2026-53324, CVE-2026-53357, CVE-2026-53358, CVE-2026-53360, CVE-2026-53364, CVE-2026-53365, CVE-2026-53367, CVE-2026-53368, CVE-2026-53369, CVE-2026-53370, CVE-2026-53371, CVE-2026-53372, CVE-2026-53373, CVE-2026-53374, CVE-2026-53375, CVE-2026-53376, CVE-2026-53377, CVE-2026-53378, CVE-2026-53379, CVE-2026-53380, CVE-2026-63837, CVE-2026-63838, CVE-2026-63839, CVE-2026-63840, CVE-2026-63841, CVE-2026-63842, CVE-2026-63843, CVE-2026-63844, CVE-2026-63845, CVE-2026-63846, CVE-2026-63847, CVE-2026-63848, CVE-2026-63849, CVE-2026-63850, CVE-2026-63851, CVE-2026-63852, CVE-2026-63853, CVE-2026-63854, CVE-2026-63855, CVE-2026-63856, CVE-2026-63857, CVE-2026-63858, CVE-2026-63859, CVE-2026-63860, CVE-2026-63861, CVE-2026-63862, CVE-2026-63863, CVE-2026-63864, CVE-2026-63865, CVE-2026-63866, CVE-2026-63875, CVE-2026-63876, CVE-2026-63877, CVE-2026-63878, CVE-2026-63879, CVE-2026-63880, CVE-2026-63881, CVE-2026-63882, CVE-2026-63883, CVE-2026-63884, CVE-2026-63886, CVE-2026-63887, CVE-2026-63888, CVE-2026-63889, CVE-2026-63890, CVE-2026-63891, CVE-2026-63892, CVE-2026-63893, CVE-2026-63894, CVE-2026-63895, CVE-2026-63896, CVE-2026-63897, CVE-2026-63898, CVE-2026-63899, CVE-2026-63900, CVE-2026-63901, CVE-2026-63902, CVE-2026-63903, CVE-2026-63904, CVE-2026-63905, CVE-2026-63906, CVE-2026-63907, CVE-2026-63908, CVE-2026-63909, CVE-2026-63910, CVE-2026-63911, CVE-2026-63912, CVE-2026-63913, CVE-2026-63914, CVE-2026-63915, CVE-2026-63916, CVE-2026-63917, CVE-2026-63918, CVE-2026-63919, CVE-2026-63920, CVE-2026-63921, CVE-2026-63922, CVE-2026-63923, CVE-2026-63924, CVE-2026-63925, CVE-2026-63926, CVE-2026-63927, CVE-2026-63928, CVE-2026-63929, CVE-2026-63930, CVE-2026-63931, CVE-2026-63932, CVE-2026-63933, CVE-2026-63934, CVE-2026-63935, CVE-2026-63936, CVE-2026-63937, CVE-2026-63938, CVE-2026-63939, CVE-2026-63940, CVE-2026-63941, CVE-2026-63942, CVE-2026-63943, CVE-2026-63944, CVE-2026-63945, CVE-2026-63946, CVE-2026-63947, CVE-2026-63948, CVE-2026-63949, CVE-2026-63950, CVE-2026-63951, CVE-2026-63952, CVE-2026-63953, CVE-2026-63954, CVE-2026-63955, CVE-2026-63956, CVE-2026-63957, CVE-2026-63958, CVE-2026-63959, CVE-2026-63960, CVE-2026-63961, CVE-2026-63962, CVE-2026-63963, CVE-2026-63964, CVE-2026-63965, CVE-2026-63966, CVE-2026-63967, CVE-2026-63968, CVE-2026-63969, CVE-2026-63970, CVE-2026-63971, CVE-2026-63972, CVE-2026-63973, CVE-2026-63974, CVE-2026-63975, CVE-2026-63976, CVE-2026-63977, CVE-2026-63978, CVE-2026-63979, CVE-2026-63980, CVE-2026-63981, CVE-2026-63982, CVE-2026-63983, CVE-2026-63984, CVE-2026-63985, CVE-2026-63986, CVE-2026-63987, CVE-2026-63988, CVE-2026-63989, CVE-2026-63990, CVE-2026-63991, CVE-2026-63992, CVE-2026-63993, CVE-2026-63994, CVE-2026-63995, CVE-2026-63996, CVE-2026-63997, CVE-2026-63998, CVE-2026-63999, CVE-2026-64000, CVE-2026-64001, CVE-2026-64002, CVE-2026-64003, CVE-2026-64004, CVE-2026-64005, CVE-2026-64006, CVE-2026-64007, CVE-2026-64008, CVE-2026-64009, CVE-2026-64010, CVE-2026-64011, CVE-2026-64012, CVE-2026-64013, CVE-2026-64014, CVE-2026-64015, CVE-2026-64017, CVE-2026-64018, CVE-2026-64019, CVE-2026-64020, CVE-2026-64021, CVE-2026-64022, CVE-2026-64023, CVE-2026-64024, CVE-2026-64025, CVE-2026-64026, CVE-2026-64027, CVE-2026-64029, CVE-2026-64030, CVE-2026-64031, CVE-2026-64032, CVE-2026-64033, CVE-2026-64034, CVE-2026-64035, CVE-2026-64036, CVE-2026-64037, CVE-2026-64038, CVE-2026-64039, CVE-2026-64040, CVE-2026-64041, CVE-2026-64042, CVE-2026-64043, CVE-2026-64044, CVE-2026-64045, CVE-2026-64046, CVE-2026-64047, CVE-2026-64048, CVE-2026-64049, CVE-2026-64050, CVE-2026-64051, CVE-2026-64052, CVE-2026-64053, CVE-2026-64054, CVE-2026-64055, CVE-2026-64056, CVE-2026-64057, CVE-2026-64058, CVE-2026-64059, CVE-2026-64060, CVE-2026-64061, CVE-2026-64062, CVE-2026-64063, CVE-2026-64064, CVE-2026-64065, CVE-2026-64066, CVE-2026-64067, CVE-2026-64068, CVE-2026-64069, CVE-2026-64070, CVE-2026-64071, CVE-2026-64072, CVE-2026-64073, CVE-2026-64074, CVE-2026-64075, CVE-2026-64076, CVE-2026-64077, CVE-2026-64078, CVE-2026-64079, CVE-2026-64080, CVE-2026-64081, CVE-2026-64082, CVE-2026-64083, CVE-2026-64084, CVE-2026-64085, CVE-2026-64086, CVE-2026-64087, CVE-2026-64088, CVE-2026-64089, CVE-2026-64090, CVE-2026-64091, CVE-2026-64093, CVE-2026-64094, CVE-2026-64095, CVE-2026-64096, CVE-2026-64097, CVE-2026-64098, CVE-2026-64099, CVE-2026-64100, CVE-2026-64101, CVE-2026-64102, CVE-2026-64103, CVE-2026-64104, CVE-2026-64105, CVE-2026-64106, CVE-2026-64107, CVE-2026-64108, CVE-2026-64109, CVE-2026-64110, CVE-2026-64111, CVE-2026-64112, CVE-2026-64113, CVE-2026-64114, CVE-2026-64115, CVE-2026-64116, CVE-2026-64117, CVE-2026-64118, CVE-2026-64119, CVE-2026-64120, CVE-2026-64121, CVE-2026-64122, CVE-2026-64123, CVE-2026-64124, CVE-2026-64125, CVE-2026-64126, CVE-2026-64127, CVE-2026-64128, CVE-2026-64129, CVE-2026-64130, CVE-2026-64131, CVE-2026-64132, CVE-2026-64133, CVE-2026-64134, CVE-2026-64135, CVE-2026-64136, CVE-2026-64137, CVE-2026-64138, CVE-2026-64139, CVE-2026-64140, CVE-2026-64141, CVE-2026-64142, CVE-2026-64143, CVE-2026-64144, CVE-2026-64145, CVE-2026-64146, CVE-2026-64147, CVE-2026-64148, CVE-2026-64149, CVE-2026-64150, CVE-2026-64151, CVE-2026-64152, CVE-2026-64153, CVE-2026-64154, CVE-2026-64155, CVE-2026-64156, CVE-2026-64157, CVE-2026-64158, CVE-2026-64159, CVE-2026-64160, CVE-2026-64161, CVE-2026-64162, CVE-2026-64163, CVE-2026-64164, CVE-2026-64165, CVE-2026-64166, CVE-2026-64167, CVE-2026-64168, CVE-2026-64169, CVE-2026-64170, CVE-2026-64171, CVE-2026-64172, CVE-2026-64173, CVE-2026-64174, CVE-2026-64175, CVE-2026-64176, CVE-2026-64177, CVE-2026-64178, CVE-2026-64179, CVE-2026-64180, CVE-2026-64181, CVE-2026-64182, CVE-2026-64183, CVE-2026-64184, CVE-2026-64185, CVE-2026-64186)
ubuntu.comJul 23, 2026extracted
USN-8569-1: Linux kernel (HWE) vulnerabilities
It was discovered that some AMD processors did not properly clear data in the floating point divider unit during speculative execution. A local attacker could use this to expose sensitive information. (CVE-2025-54505) It was discovered that some AMD Zen 2 processors did not properly isolate shared resources in the operation cache. A local attacker could possibly use this issue to corrupt instructions executed at a higher privilege level, resulting in privilege escalation. (CVE-2025-54518) It was discovered that the Linux kernel did not properly handle shared page fragments during socket buffer operations, collectively known as Dirty Frag. A logic flaw existed in the XFRM ESP-in-TCP subsystem and in the RxRPC networking subsystem when processing paged fragments. A local attacker could use this to escalate privileges, or possibly escape a container. (CVE-2026-43284, CVE-2026-43500, CVE-2026-45998, CVE-2026-46000) It was discovered that a logic flaw existed in the XFRM ESP-in-TCP subsystem in the Linux kernel when handling socket buffer fragments. This flaw is known as Fragnesia. A local attacker could use this to escalate privileges, or possibly escape a container. (CVE-2026-43503, CVE-2026-46300) Qualys discovered that a race condition existed in the ptrace subsystem of the Linux kernel when privileged processes are exiting. An unprivileged local attacker could use this issue to expose sensitive information. (CVE-2026-46333) Tristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0 contain a memory leak when handling AppArmor notifications. A local attacker could use this to cause resource exhaustion. (CVE-2026-47326) Tristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0 contain a NULL pointer dereference when handling AppArmor notifications. A local attacker could use this to cause a kernel oops. (CVE-2026-47327) Tristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0 contained an invalid free when handling AppArmor notifications. A local attacker could use this to corrupt kernel memory. (CVE-2026-47328) Tristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0 contained insufficient validation of AppArmor notification responses. A local attacker could use this to allow crafted responses to be processed. (CVE-2026-47329) Tristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0 used an uninitialized variable when handling AppArmor notifications. A local attacker could use this to cause incorrect caching of data. (CVE-2026-47330) Tristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0 contained an out-of-bounds (OOB) read when handling AppArmor notifications. A local attacker could use this to cause information disclosure of kernel memory. (CVE-2026-47332) Tristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0 contained a out-of-bounds (OOB) read when handling AppArmor notifications. A local attacker could use this to cause kernel memory corruption and, theoretically, influence processing of AppArmor policies. (CVE-2026-47333) Tristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0 contained incorrect holding of locks when handling AppArmor notifications. A local attacker could use this to cause a kernel panic or deadlock. (CVE-2026-47334) Tristan Madani and Trevor Lawrence have each independently discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0 contained a NULL pointer dereference when handling AppArmor network socket mediation. A local attacker could use this to cause a kernel oops. (CVE-2026-47337) 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: - PSP security protocol; - ARM64 architecture; - PowerPC architecture; - RISC-V architecture; - S390 architecture; - User-Mode Linux (UML); - x86 architecture; - Block layer subsystem; - Cryptographic API; - Intel NPU Driver; - DRBD Distributed Replicated Block Device drivers; - Rados block device (RBD) driver; - Ublk userspace block driver; - Compressed RAM block device driver; - Bluetooth drivers; - Bus devices; - Character device driver; - TPM device driver; - Clock framework and drivers; - CPU frequency scaling framework; - Hardware crypto device drivers; - EDAC drivers; - EFI core; - FWCTL subsystem; - GPU drivers; - Greybus drivers; - HID subsystem; - Microsoft Hyper-V drivers; - Hardware monitoring drivers; - I2C subsystem; - I3C subsystem; - IIO subsystem; - InfiniBand drivers; - Input Device core drivers; - IOMMU subsystem; - LED subsystem; - Mailbox framework; - Multiple devices driver; - Media drivers; - NVIDIA Tegra memory controller driver; - IBM Advanced System Management driver; - MTD block device drivers; - Network drivers; - Ethernet bonding driver; - Mellanox network drivers; - Microsoft Azure Network Adapter (MANA) driver; - STMicroelectronics network drivers; - MediaTek network drivers; - NTB driver; - NVME drivers; - Device tree and open firmware driver; - PCI subsystem; - Pin controllers subsystem; - Chrome hardware platform drivers; - ACPI WMI driver; - x86 platform drivers; - Generic PM domains; - MediaTek PM domains; - Power supply drivers; - Remote Processor subsystem; - MPAM driver; - Amlogic Meson reset controller drivers; - S/390 drivers; - SCSI subsystem; - NVIDIA Tegra Control Backbone (CBB) driver; - SPI subsystem; - Greybus lights staging drivers; - Media staging drivers; - Realtek RTL8723BS SDIO drivers; - SM750 framebuffer staging driver; - TCM subsystem; - Thermal drivers; - TTY drivers; - USB Device Class drivers; - ULPI bus; - USB Gadget drivers; - USB Type-C support driver; - TI TPS6598x USB Power Delivery controller driver; - USB over IP driver; - vDPA drivers; - VFIO drivers; - Framebuffer layer; - TSM AMD SEV Guest driver; - Xen hypervisor drivers; - 9P distributed file system; - File systems infrastructure; - AFS file system; - BTRFS file system; - Ceph distributed file system; - EROFS file system; - Ext4 file system; - F2FS file system; - FUSE (File system in Userspace); - GFS2 file system; - HFS+ file system; - HugeTLB file system; - Journaling layer for block devices (JBD2); - Network file system (NFS) server daemon; - NILFS2 file system; - File system notification infrastructure; - NTFS3 file system; - OCFS2 file system; - Overlay file system; - Diskquota system; - SMB network file system; - Tracing file system; - UDF file system; - XFS file system; - DRM TTM subsystem; - Codetag library; - Control group (cgroup); - Kernel CPU control infrastructure; - Memory management; - QorIQ DPAA2 FSL-MC bus driver; - Freescale ENETC Ethernet drivers; - Memory Management; - KVM subsystem; - padata parallel execution mechanism; - PPP protocol drivers and compressors; - Bluetooth subsystem; - Networking core; - Netfilter; - Network traffic control; - Tracing infrastructure; - User-space API (UAPI); - io_uring subsystem; - IPC subsystem; - Audit subsystem; - BPF subsystem; - Kernel exit() syscall; - Kernel fork() syscall; - Kernel futex primitives; - Locking primitives; - Padata parallel execution mechanism; - Scheduler infrastructure; - Timer subsystem; - Cryptographic library; - Scatterlist API; - Heterogeneous memory management; - KASAN memory debugging framework; - 802.1Q VLAN protocol; - B.A.T.M.A.N. meshing protocol; - Ethernet bridge; - CAIF protocol; - CAN network layer; - Ceph Core library; - Distributed Switch Architecture; - IPv4 networking; - IPv6 networking; - MAC80211 subsystem; - Multipath TCP; - NFC subsystem; - Open vSwitch; - Packet sockets; - Phonet protocol; - Qualcomm IPC Router (QRTR); - RDS protocol; - RxRPC session sockets; - SCTP protocol; - SMC sockets; - Stream parser; - TIPC protocol; - TLS protocol; - Unix domain sockets; - VMware vSockets driver; - XFRM subsystem; - Integrity Measurement Architecture(IMA) framework; - Landlock security; - SELinux security module; - ALSA framework; - Generic PCM loopback sound driver; - FireWire sound drivers; - HD-audio driver; - Creative Sound Blaster X-Fi driver; - QCOM ASoC drivers; - SOF drivers; - STI ASoC drivers; - USB sound devices; - Objtool; (CVE-2026-31532, CVE-2026-31574, CVE-2026-31575, CVE-2026-31576, CVE-2026-31577, CVE-2026-31578, CVE-2026-31579, CVE-2026-31580, CVE-2026-31581, CVE-2026-31582, CVE-2026-31583, CVE-2026-31584, CVE-2026-31585, CVE-2026-31586, CVE-2026-31587, CVE-2026-31588, CVE-2026-31589, CVE-2026-31590, CVE-2026-31591, CVE-2026-31592, CVE-2026-31593, CVE-2026-31594, CVE-2026-31595, CVE-2026-31596, CVE-2026-31597, CVE-2026-31598, CVE-2026-31599, CVE-2026-31600, CVE-2026-31601, CVE-2026-31602, CVE-2026-31603, CVE-2026-31604, CVE-2026-31605, CVE-2026-31606, CVE-2026-31607, CVE-2026-31608, CVE-2026-31609, CVE-2026-31610, CVE-2026-31611, CVE-2026-31612, CVE-2026-31613, CVE-2026-31614, CVE-2026-31615, CVE-2026-31616, CVE-2026-31617, CVE-2026-31618, CVE-2026-31619, CVE-2026-31620, CVE-2026-31621, CVE-2026-31622, CVE-2026-31623, CVE-2026-31624, CVE-2026-31625, CVE-2026-31626, CVE-2026-31627, CVE-2026-31628, CVE-2026-31629, CVE-2026-31686, CVE-2026-31694, CVE-2026-31696, CVE-2026-31697, CVE-2026-31698, CVE-2026-31699, CVE-2026-31700, CVE-2026-31701, CVE-2026-31702, CVE-2026-31703, CVE-2026-31704, CVE-2026-31705, CVE-2026-31706, CVE-2026-31707, CVE-2026-31708, CVE-2026-31709, CVE-2026-31710, CVE-2026-31711, CVE-2026-31712, CVE-2026-31713, CVE-2026-31714, CVE-2026-31715, CVE-2026-31716, CVE-2026-31717, CVE-2026-31718, CVE-2026-31719, CVE-2026-43058, CVE-2026-43071, CVE-2026-43072, CVE-2026-43073, CVE-2026-43348, CVE-2026-43349, CVE-2026-43350, CVE-2026-43490, CVE-2026-43491, CVE-2026-43492, CVE-2026-43493, CVE-2026-43494, CVE-2026-43495, CVE-2026-43496, CVE-2026-43497, CVE-2026-43498, CVE-2026-43499, CVE-2026-43501, CVE-2026-43502, CVE-2026-45834, CVE-2026-45835, CVE-2026-45836, CVE-2026-45837, CVE-2026-45838, CVE-2026-45839, CVE-2026-45840, CVE-2026-45841, CVE-2026-45842, CVE-2026-45843, CVE-2026-45844, CVE-2026-45845, CVE-2026-45846, CVE-2026-45986, CVE-2026-45987, CVE-2026-45988, CVE-2026-45989, CVE-2026-45990, CVE-2026-45991, CVE-2026-45994, CVE-2026-45995, CVE-2026-45996, CVE-2026-45997, CVE-2026-45999, CVE-2026-46001, CVE-2026-46002, CVE-2026-46003, CVE-2026-46004, CVE-2026-46005, CVE-2026-46006, CVE-2026-46007, CVE-2026-46008, CVE-2026-46009, CVE-2026-46010, CVE-2026-46011, CVE-2026-46012, CVE-2026-46013, CVE-2026-46014, CVE-2026-46015, CVE-2026-46016, CVE-2026-46018, CVE-2026-46019, CVE-2026-46020, CVE-2026-46021, CVE-2026-46022, CVE-2026-46023, CVE-2026-46024, CVE-2026-46025, CVE-2026-46026, CVE-2026-46027, CVE-2026-46028, CVE-2026-46029, CVE-2026-46030, CVE-2026-46031, CVE-2026-46032, CVE-2026-46033, CVE-2026-46034, CVE-2026-46035, CVE-2026-46036, CVE-2026-46037, CVE-2026-46038, CVE-2026-46039, CVE-2026-46040, CVE-2026-46041, CVE-2026-46042, CVE-2026-46043, CVE-2026-46044, CVE-2026-46045, CVE-2026-46046, CVE-2026-46047, CVE-2026-46049, CVE-2026-46050, CVE-2026-46051, CVE-2026-46052, CVE-2026-46053, CVE-2026-46054, CVE-2026-46056, CVE-2026-46057, CVE-2026-46058, CVE-2026-46059, CVE-2026-46060, CVE-2026-46061, CVE-2026-46062, CVE-2026-46063, CVE-2026-46064, CVE-2026-46065, CVE-2026-46066, CVE-2026-46067, CVE-2026-46068, CVE-2026-46069, CVE-2026-46070, CVE-2026-46071, CVE-2026-46072, CVE-2026-46073, CVE-2026-46074, CVE-2026-46075, CVE-2026-46076, CVE-2026-46077, CVE-2026-46078, CVE-2026-46079, CVE-2026-46080, CVE-2026-46081, CVE-2026-46082, CVE-2026-46083, CVE-2026-46084, CVE-2026-46085, CVE-2026-46086, CVE-2026-46087, CVE-2026-46088, CVE-2026-46089, CVE-2026-46090, CVE-2026-46091, CVE-2026-46092, CVE-2026-46093, CVE-2026-46094, CVE-2026-46095, CVE-2026-46096, CVE-2026-46097, CVE-2026-46098, CVE-2026-46099, CVE-2026-46100, CVE-2026-46101, CVE-2026-46102, CVE-2026-46103, CVE-2026-46104, CVE-2026-46105, CVE-2026-46106, CVE-2026-46107, CVE-2026-46108, CVE-2026-46109, CVE-2026-46110, CVE-2026-46111, CVE-2026-46112, CVE-2026-46113, CVE-2026-46114, CVE-2026-46115, CVE-2026-46116, CVE-2026-46117, CVE-2026-46118, CVE-2026-46119, CVE-2026-46120, CVE-2026-46121, CVE-2026-46122, CVE-2026-46123, CVE-2026-46124, CVE-2026-46125, CVE-2026-46126, CVE-2026-46127, CVE-2026-46128, CVE-2026-46129, CVE-2026-46130, CVE-2026-46131, CVE-2026-46132, CVE-2026-46133, CVE-2026-46134, CVE-2026-46135, CVE-2026-46136, CVE-2026-46137, CVE-2026-46138, CVE-2026-46139, CVE-2026-46140, CVE-2026-46141, CVE-2026-46142, CVE-2026-46143, CVE-2026-46144, CVE-2026-46145, CVE-2026-46146, CVE-2026-46147, CVE-2026-46148, CVE-2026-46149, CVE-2026-46150, CVE-2026-46151, CVE-2026-46152, CVE-2026-46153, CVE-2026-46154, CVE-2026-46155, CVE-2026-46156, CVE-2026-46157, CVE-2026-46158, CVE-2026-46159, CVE-2026-46160, CVE-2026-46161, CVE-2026-46162, CVE-2026-46163, CVE-2026-46164, CVE-2026-46165, CVE-2026-46166, CVE-2026-46167, CVE-2026-46168, CVE-2026-46169, CVE-2026-46170, CVE-2026-46171, CVE-2026-46172, CVE-2026-46173, CVE-2026-46174, CVE-2026-46175, CVE-2026-46176, CVE-2026-46177, CVE-2026-46178, CVE-2026-46179, CVE-2026-46180, CVE-2026-46181, CVE-2026-46182, CVE-2026-46183, CVE-2026-46184, CVE-2026-46185, CVE-2026-46186, CVE-2026-46187, CVE-2026-46188, CVE-2026-46189, CVE-2026-46190, CVE-2026-46191, CVE-2026-46192, CVE-2026-46193, CVE-2026-46194, CVE-2026-46195, CVE-2026-46196, CVE-2026-46197, CVE-2026-46198, CVE-2026-46199, CVE-2026-46200, CVE-2026-46201, CVE-2026-46202, CVE-2026-46203, CVE-2026-46204, CVE-2026-46205, CVE-2026-46206, CVE-2026-46207, CVE-2026-46208, CVE-2026-46209, CVE-2026-46210, CVE-2026-46211, CVE-2026-46212, CVE-2026-46213, CVE-2026-46214, CVE-2026-46215, CVE-2026-46216, CVE-2026-46218, CVE-2026-46219, CVE-2026-46220, CVE-2026-46221, CVE-2026-46222, CVE-2026-46223, CVE-2026-46224, CVE-2026-46225, CVE-2026-46226, CVE-2026-46227, CVE-2026-46228, CVE-2026-46229, CVE-2026-46230, CVE-2026-46231, CVE-2026-46232, CVE-2026-46233, CVE-2026-46234, CVE-2026-46235, CVE-2026-46236, CVE-2026-46238, CVE-2026-46239, CVE-2026-46240, CVE-2026-46241, CVE-2026-46242, CVE-2026-46243, CVE-2026-46244, CVE-2026-46273, CVE-2026-46274, CVE-2026-46275, CVE-2026-46276, CVE-2026-46277, CVE-2026-46278, CVE-2026-46279, CVE-2026-46280, CVE-2026-46281, CVE-2026-46282, CVE-2026-46283, CVE-2026-46284, CVE-2026-46285, CVE-2026-46286, CVE-2026-46287, CVE-2026-46288, CVE-2026-46289, CVE-2026-46290, CVE-2026-46291, CVE-2026-46292, CVE-2026-46293, CVE-2026-46294, CVE-2026-46295, CVE-2026-46296, CVE-2026-46297, CVE-2026-46298, CVE-2026-46299, CVE-2026-46301, CVE-2026-46302, CVE-2026-46303, CVE-2026-46304, CVE-2026-46305, CVE-2026-46306, CVE-2026-46307, CVE-2026-46308, CVE-2026-46309, CVE-2026-46310, CVE-2026-46311, CVE-2026-46312, CVE-2026-46313, CVE-2026-46314, CVE-2026-46315, CVE-2026-46316, CVE-2026-46317, CVE-2026-46318, CVE-2026-46319, CVE-2026-46320, CVE-2026-46321, CVE-2026-46322, CVE-2026-46323, CVE-2026-46324, CVE-2026-46332, CVE-2026-52904, CVE-2026-52905, CVE-2026-52906, CVE-2026-52907, CVE-2026-52911, CVE-2026-52912, CVE-2026-52913, CVE-2026-52914, CVE-2026-52915, CVE-2026-52916, CVE-2026-52918, CVE-2026-52919, CVE-2026-52920, CVE-2026-52921, CVE-2026-52922, CVE-2026-52923, CVE-2026-52925, CVE-2026-52926, CVE-2026-52927, CVE-2026-52928, CVE-2026-52931, CVE-2026-52932, CVE-2026-52933, CVE-2026-52934, CVE-2026-52936, CVE-2026-52937, CVE-2026-52941, CVE-2026-52943, CVE-2026-52944, CVE-2026-52949, CVE-2026-52950, CVE-2026-52951, CVE-2026-52952, CVE-2026-52953, CVE-2026-52954, CVE-2026-52955, CVE-2026-52956, CVE-2026-52957, CVE-2026-52958, CVE-2026-52959, CVE-2026-52960, CVE-2026-52961, CVE-2026-52962, CVE-2026-52963, CVE-2026-52964, CVE-2026-52965, CVE-2026-52967, CVE-2026-52968, CVE-2026-52969, CVE-2026-52970, CVE-2026-52971, CVE-2026-52973, CVE-2026-52974, CVE-2026-52975, CVE-2026-52976, CVE-2026-52977, CVE-2026-52978, CVE-2026-52979, CVE-2026-52980, CVE-2026-52981, CVE-2026-52982, CVE-2026-52983, CVE-2026-52984, CVE-2026-52985, CVE-2026-52986, CVE-2026-52987, CVE-2026-52988, CVE-2026-52989, CVE-2026-52990, CVE-2026-52991, CVE-2026-52992, CVE-2026-52993, CVE-2026-52994, CVE-2026-52995, CVE-2026-52996, CVE-2026-52997, CVE-2026-52998, CVE-2026-52999, CVE-2026-53000, CVE-2026-53001, CVE-2026-53002, CVE-2026-53003, CVE-2026-53004, CVE-2026-53005, CVE-2026-53006, CVE-2026-53007, CVE-2026-53008, CVE-2026-53009, CVE-2026-53010, CVE-2026-53011, CVE-2026-53012, CVE-2026-53013, CVE-2026-53014, CVE-2026-53015, CVE-2026-53016, CVE-2026-53017, CVE-2026-53018, CVE-2026-53019, CVE-2026-53020, CVE-2026-53021, CVE-2026-53022, CVE-2026-53023, CVE-2026-53024, CVE-2026-53025, CVE-2026-53026, CVE-2026-53027, CVE-2026-53028, CVE-2026-53029, CVE-2026-53030, CVE-2026-53031, CVE-2026-53032, CVE-2026-53033, CVE-2026-53034, CVE-2026-53035, CVE-2026-53036, CVE-2026-53037, CVE-2026-53038, CVE-2026-53039, CVE-2026-53040, CVE-2026-53041, CVE-2026-53042, CVE-2026-53043, CVE-2026-53044, CVE-2026-53045, CVE-2026-53046, CVE-2026-53047, CVE-2026-53048, CVE-2026-53049, CVE-2026-53050, CVE-2026-53051, CVE-2026-53052, CVE-2026-53053, CVE-2026-53054, CVE-2026-53055, CVE-2026-53056, CVE-2026-53057, CVE-2026-53058, CVE-2026-53059, CVE-2026-53060, CVE-2026-53061, CVE-2026-53062, CVE-2026-53063, CVE-2026-53064, CVE-2026-53065, CVE-2026-53066, CVE-2026-53067, CVE-2026-53068, CVE-2026-53069, CVE-2026-53070, CVE-2026-53071, CVE-2026-53072, CVE-2026-53073, CVE-2026-53074, CVE-2026-53075, CVE-2026-53076, CVE-2026-53077, CVE-2026-53078, CVE-2026-53079, CVE-2026-53080, CVE-2026-53081, CVE-2026-53082, CVE-2026-53083, CVE-2026-53084, CVE-2026-53085, CVE-2026-53086, CVE-2026-53087, CVE-2026-53088, CVE-2026-53089, CVE-2026-53090, CVE-2026-53091, CVE-2026-53092, CVE-2026-53093, CVE-2026-53094, CVE-2026-53095, CVE-2026-53096, CVE-2026-53097, CVE-2026-53098, CVE-2026-53099, CVE-2026-53100, CVE-2026-53101, CVE-2026-53102, CVE-2026-53103, CVE-2026-53104, CVE-2026-53105, CVE-2026-53106, CVE-2026-53107, CVE-2026-53108, CVE-2026-53109, CVE-2026-53110, CVE-2026-53111, CVE-2026-53112, CVE-2026-53113, CVE-2026-53114, CVE-2026-53115, CVE-2026-53116, CVE-2026-53117, CVE-2026-53118, CVE-2026-53119, CVE-2026-53120, CVE-2026-53121, CVE-2026-53122, CVE-2026-53123, CVE-2026-53124, CVE-2026-53125, CVE-2026-53126, CVE-2026-53127, CVE-2026-53128, CVE-2026-53129, CVE-2026-53130, CVE-2026-53174, CVE-2026-53277, CVE-2026-53278, CVE-2026-53279, CVE-2026-53280, CVE-2026-53281, CVE-2026-53282, CVE-2026-53283, CVE-2026-53284, CVE-2026-53285, CVE-2026-53286, CVE-2026-53287, CVE-2026-53288, CVE-2026-53289, CVE-2026-53290, CVE-2026-53291, CVE-2026-53292, CVE-2026-53293, CVE-2026-53294, CVE-2026-53295, CVE-2026-53296, CVE-2026-53297, CVE-2026-53298, CVE-2026-53299, CVE-2026-53300, CVE-2026-53301, CVE-2026-53302, CVE-2026-53303, CVE-2026-53304, CVE-2026-53305, CVE-2026-53306, CVE-2026-53307, CVE-2026-53308, CVE-2026-53309, CVE-2026-53310, CVE-2026-53311, CVE-2026-53312, CVE-2026-53313, CVE-2026-53314, CVE-2026-53315, CVE-2026-53316, CVE-2026-53317, CVE-2026-53318, CVE-2026-53319, CVE-2026-53320, CVE-2026-53321, CVE-2026-53322, CVE-2026-53323, CVE-2026-53324, CVE-2026-53357, CVE-2026-53358, CVE-2026-53360, CVE-2026-53364, CVE-2026-53365)
ubuntu.comJul 20, 2026extracted
USN-8568-1: Linux kernel (OEM) vulnerabilities
It was discovered that some AMD Zen 2 processors did not properly isolate shared resources in the operation cache. A local attacker could possibly use this issue to corrupt instructions executed at a higher privilege level, resulting in privilege escalation. (CVE-2025-54518) 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: - PSP security protocol; - ARM64 architecture; - PowerPC architecture; - RISC-V architecture; - S390 architecture; - User-Mode Linux (UML); - x86 architecture; - Block layer subsystem; - Cryptographic API; - Intel NPU Driver; - DRBD Distributed Replicated Block Device drivers; - Ublk userspace block driver; - Bluetooth drivers; - Bus devices; - Character device driver; - Clock framework and drivers; - CPU frequency scaling framework; - Hardware crypto device drivers; - EDAC drivers; - EFI core; - FWCTL subsystem; - GPU drivers; - HID subsystem; - I3C subsystem; - InfiniBand drivers; - IOMMU subsystem; - Mailbox framework; - Multiple devices driver; - Media drivers; - NVIDIA Tegra memory controller driver; - MTD block device drivers; - Network drivers; - Ethernet bonding driver; - Mellanox network drivers; - Microsoft Azure Network Adapter (MANA) driver; - STMicroelectronics network drivers; - MediaTek network drivers; - NVME drivers; - PCI subsystem; - Pin controllers subsystem; - Chrome hardware platform drivers; - ACPI WMI driver; - x86 platform drivers; - Generic PM domains; - MediaTek PM domains; - Power supply drivers; - MPAM driver; - Amlogic Meson reset controller drivers; - S/390 drivers; - SCSI subsystem; - NVIDIA Tegra Control Backbone (CBB) driver; - SPI subsystem; - Greybus lights staging drivers; - Media staging drivers; - Realtek RTL8723BS SDIO drivers; - TCM subsystem; - TTY drivers; - USB Device Class drivers; - ULPI bus; - USB Type-C support driver; - TI TPS6598x USB Power Delivery controller driver; - vDPA drivers; - VFIO drivers; - Framebuffer layer; - TSM AMD SEV Guest driver; - Xen hypervisor drivers; - File systems infrastructure; - BTRFS file system; - Ceph distributed file system; - EROFS file system; - F2FS file system; - FUSE (File system in Userspace); - GFS2 file system; - HFS+ file system; - HugeTLB file system; - Network file system (NFS) server daemon; - NILFS2 file system; - File system notification infrastructure; - NTFS3 file system; - OCFS2 file system; - Diskquota system; - SMB network file system; - Tracing file system; - DRM TTM subsystem; - Control group (cgroup); - Kernel CPU control infrastructure; - QorIQ DPAA2 FSL-MC bus driver; - Freescale ENETC Ethernet drivers; - Memory Management; - padata parallel execution mechanism; - PPP protocol drivers and compressors; - Bluetooth subsystem; - Networking core; - Netfilter; - Network traffic control; - io_uring subsystem; - IPC subsystem; - Audit subsystem; - BPF subsystem; - Kernel exit() syscall; - Kernel fork() syscall; - Kernel futex primitives; - Padata parallel execution mechanism; - Scheduler infrastructure; - Tracing infrastructure; - Cryptographic library; - Memory management; - 802.1Q VLAN protocol; - B.A.T.M.A.N. meshing protocol; - Ethernet bridge; - Ceph Core library; - Distributed Switch Architecture; - IPv4 networking; - IPv6 networking; - MAC80211 subsystem; - Multipath TCP; - Open vSwitch; - Phonet protocol; - RDS protocol; - SCTP protocol; - SMC sockets; - TIPC protocol; - TLS protocol; - Unix domain sockets; - VMware vSockets driver; - XFRM subsystem; - Integrity Measurement Architecture(IMA) framework; - SELinux security module; - ALSA framework; - HD-audio driver; - QCOM ASoC drivers; - SOF drivers; - STI ASoC drivers; - USB sound devices; - KVM subsystem; (CVE-2026-43490, CVE-2026-43492, CVE-2026-43495, CVE-2026-43496, CVE-2026-43497, CVE-2026-43498, CVE-2026-43502, CVE-2026-45834, CVE-2026-45835, CVE-2026-45836, CVE-2026-45837, CVE-2026-45838, CVE-2026-45839, CVE-2026-45840, CVE-2026-45841, CVE-2026-45842, CVE-2026-45843, CVE-2026-45844, CVE-2026-45845, CVE-2026-45846, CVE-2026-46104, CVE-2026-46105, CVE-2026-46106, CVE-2026-46107, CVE-2026-46108, CVE-2026-46109, CVE-2026-46110, CVE-2026-46111, CVE-2026-46112, CVE-2026-46113, CVE-2026-46114, CVE-2026-46116, CVE-2026-46117, CVE-2026-46118, CVE-2026-46120, CVE-2026-46121, CVE-2026-46122, CVE-2026-46123, CVE-2026-46124, CVE-2026-46125, CVE-2026-46126, CVE-2026-46127, CVE-2026-46128, CVE-2026-46129, CVE-2026-46130, CVE-2026-46131, CVE-2026-46132, CVE-2026-46133, CVE-2026-46134, CVE-2026-46136, CVE-2026-46138, CVE-2026-46139, CVE-2026-46140, CVE-2026-46141, CVE-2026-46142, CVE-2026-46143, CVE-2026-46144, CVE-2026-46145, CVE-2026-46146, CVE-2026-46147, CVE-2026-46148, CVE-2026-46149, CVE-2026-46150, CVE-2026-46151, CVE-2026-46152, CVE-2026-46153, CVE-2026-46154, CVE-2026-46156, CVE-2026-46157, CVE-2026-46158, CVE-2026-46159, CVE-2026-46160, CVE-2026-46161, CVE-2026-46162, CVE-2026-46163, CVE-2026-46164, CVE-2026-46165, CVE-2026-46166, CVE-2026-46167, CVE-2026-46168, CVE-2026-46169, CVE-2026-46170, CVE-2026-46171, CVE-2026-46172, CVE-2026-46173, CVE-2026-46174, CVE-2026-46175, CVE-2026-46176, CVE-2026-46177, CVE-2026-46178, CVE-2026-46179, CVE-2026-46180, CVE-2026-46181, CVE-2026-46182, CVE-2026-46183, CVE-2026-46184, CVE-2026-46186, CVE-2026-46187, CVE-2026-46188, CVE-2026-46189, CVE-2026-46190, CVE-2026-46191, CVE-2026-46192, CVE-2026-46193, CVE-2026-46194, CVE-2026-46196, CVE-2026-46197, CVE-2026-46198, CVE-2026-46199, CVE-2026-46200, CVE-2026-46201, CVE-2026-46202, CVE-2026-46203, CVE-2026-46204, CVE-2026-46205, CVE-2026-46206, CVE-2026-46207, CVE-2026-46208, CVE-2026-46209, CVE-2026-46210, CVE-2026-46211, CVE-2026-46212, CVE-2026-46213, CVE-2026-46214, CVE-2026-46215, CVE-2026-46216, CVE-2026-46218, CVE-2026-46219, CVE-2026-46220, CVE-2026-46221, CVE-2026-46222, CVE-2026-46223, CVE-2026-46224, CVE-2026-46225, CVE-2026-46226, CVE-2026-46227, CVE-2026-46228, CVE-2026-46229, CVE-2026-46230, CVE-2026-46231, CVE-2026-46232, CVE-2026-46233, CVE-2026-46234, CVE-2026-46235, CVE-2026-46236, CVE-2026-46238, CVE-2026-46239, CVE-2026-46240, CVE-2026-46241, CVE-2026-46242, CVE-2026-46273, CVE-2026-46274, CVE-2026-46275, CVE-2026-46290, CVE-2026-46291, CVE-2026-46292, CVE-2026-46293, CVE-2026-46294, CVE-2026-46295, CVE-2026-46296, CVE-2026-46297, CVE-2026-46298, CVE-2026-46299, CVE-2026-46301, CVE-2026-46302, CVE-2026-46303, CVE-2026-46304, CVE-2026-46305, CVE-2026-46306, CVE-2026-46307, CVE-2026-46308, CVE-2026-46309, CVE-2026-46310, CVE-2026-46311, CVE-2026-46312, CVE-2026-46313, CVE-2026-46314, CVE-2026-46315, CVE-2026-46317, CVE-2026-46318, CVE-2026-46319, CVE-2026-46320, CVE-2026-46321, CVE-2026-46322, CVE-2026-46324, CVE-2026-52911, CVE-2026-52912, CVE-2026-52913, CVE-2026-52914, CVE-2026-52915, CVE-2026-52916, CVE-2026-52918, CVE-2026-52919, CVE-2026-52920, CVE-2026-52921, CVE-2026-52922, CVE-2026-52923, CVE-2026-52925, CVE-2026-52926, CVE-2026-52927, CVE-2026-52928, CVE-2026-52931, CVE-2026-52932, CVE-2026-52934, CVE-2026-52936, CVE-2026-52937, CVE-2026-52941, CVE-2026-52943, CVE-2026-52944, CVE-2026-52949, CVE-2026-52950, CVE-2026-52951, CVE-2026-52952, CVE-2026-52953, CVE-2026-52954, CVE-2026-52955, CVE-2026-52956, CVE-2026-52957, CVE-2026-52958, CVE-2026-52959, CVE-2026-52960, CVE-2026-52961, CVE-2026-52962, CVE-2026-52963, CVE-2026-52964, CVE-2026-52965, CVE-2026-52967, CVE-2026-52968, CVE-2026-52969, CVE-2026-52970, CVE-2026-52971, CVE-2026-52973, CVE-2026-52974, CVE-2026-52975, CVE-2026-52976, CVE-2026-52977, CVE-2026-52978, CVE-2026-52979, CVE-2026-52980, CVE-2026-52981, CVE-2026-52982, CVE-2026-52983, CVE-2026-52984, CVE-2026-52985, CVE-2026-52986, CVE-2026-52987, CVE-2026-52988, CVE-2026-52989, CVE-2026-52990, CVE-2026-52991, CVE-2026-52992, CVE-2026-52993, CVE-2026-52994, CVE-2026-52995, CVE-2026-52996, CVE-2026-52997, CVE-2026-52998, CVE-2026-52999, CVE-2026-53000, CVE-2026-53001, CVE-2026-53002, CVE-2026-53003, CVE-2026-53004, CVE-2026-53005, CVE-2026-53006, CVE-2026-53007, CVE-2026-53008, CVE-2026-53009, CVE-2026-53010, CVE-2026-53011, CVE-2026-53012, CVE-2026-53013, CVE-2026-53014, CVE-2026-53015, CVE-2026-53016, CVE-2026-53017, CVE-2026-53018, CVE-2026-53019, CVE-2026-53020, CVE-2026-53021, CVE-2026-53022, CVE-2026-53023, CVE-2026-53024, CVE-2026-53025, CVE-2026-53026, CVE-2026-53027, CVE-2026-53028, CVE-2026-53029, CVE-2026-53030, CVE-2026-53031, CVE-2026-53032, CVE-2026-53033, CVE-2026-53034, CVE-2026-53035, CVE-2026-53036, CVE-2026-53037, CVE-2026-53038, CVE-2026-53039, CVE-2026-53040, CVE-2026-53041, CVE-2026-53042, CVE-2026-53043, CVE-2026-53044, CVE-2026-53045, CVE-2026-53046, CVE-2026-53047, CVE-2026-53048, CVE-2026-53049, CVE-2026-53050, CVE-2026-53051, CVE-2026-53052, CVE-2026-53053, CVE-2026-53054, CVE-2026-53055, CVE-2026-53056, CVE-2026-53057, CVE-2026-53058, CVE-2026-53059, CVE-2026-53060, CVE-2026-53061, CVE-2026-53062, CVE-2026-53063, CVE-2026-53064, CVE-2026-53065, CVE-2026-53066, CVE-2026-53067, CVE-2026-53068, CVE-2026-53069, CVE-2026-53070, CVE-2026-53071, CVE-2026-53072, CVE-2026-53073, CVE-2026-53074, CVE-2026-53075, CVE-2026-53076, CVE-2026-53077, CVE-2026-53078, CVE-2026-53079, CVE-2026-53080, CVE-2026-53081, CVE-2026-53082, CVE-2026-53083, CVE-2026-53084, CVE-2026-53085, CVE-2026-53086, CVE-2026-53087, CVE-2026-53088, CVE-2026-53089, CVE-2026-53090, CVE-2026-53091, CVE-2026-53092, CVE-2026-53093, CVE-2026-53094, CVE-2026-53095, CVE-2026-53096, CVE-2026-53097, CVE-2026-53098, CVE-2026-53099, CVE-2026-53100, CVE-2026-53101, CVE-2026-53102, CVE-2026-53103, CVE-2026-53104, CVE-2026-53105, CVE-2026-53106, CVE-2026-53107, CVE-2026-53108, CVE-2026-53109, CVE-2026-53110, CVE-2026-53111, CVE-2026-53112, CVE-2026-53113, CVE-2026-53114, CVE-2026-53115, CVE-2026-53116, CVE-2026-53117, CVE-2026-53118, CVE-2026-53119, CVE-2026-53120, CVE-2026-53121, CVE-2026-53122, CVE-2026-53123, CVE-2026-53124, CVE-2026-53125, CVE-2026-53126, CVE-2026-53127, CVE-2026-53128, CVE-2026-53129, CVE-2026-53130, CVE-2026-53277, CVE-2026-53278, CVE-2026-53279, CVE-2026-53280, CVE-2026-53281, CVE-2026-53282, CVE-2026-53283, CVE-2026-53284, CVE-2026-53285, CVE-2026-53286, CVE-2026-53287, CVE-2026-53288, CVE-2026-53289, CVE-2026-53290, CVE-2026-53291, CVE-2026-53292, CVE-2026-53293, CVE-2026-53294, CVE-2026-53295, CVE-2026-53296, CVE-2026-53297, CVE-2026-53298, CVE-2026-53299, CVE-2026-53300, CVE-2026-53301, CVE-2026-53302, CVE-2026-53303, CVE-2026-53304, CVE-2026-53305, CVE-2026-53306, CVE-2026-53307, CVE-2026-53308, CVE-2026-53309, CVE-2026-53310, CVE-2026-53311, CVE-2026-53312, CVE-2026-53313, CVE-2026-53314, CVE-2026-53315, CVE-2026-53316, CVE-2026-53317, CVE-2026-53318, CVE-2026-53319, CVE-2026-53320, CVE-2026-53321, CVE-2026-53322, CVE-2026-53323, CVE-2026-53324, CVE-2026-53357, CVE-2026-53358, CVE-2026-53360, CVE-2026-53364, CVE-2026-53365)
ubuntu.comJul 20, 2026extracted
USN-8566-1: Linux kernel vulnerabilities
It was discovered that some AMD Zen 2 processors did not properly isolate shared resources in the operation cache. A local attacker could possibly use this issue to corrupt instructions executed at a higher privilege level, resulting in privilege escalation. (CVE-2025-54518) 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: - PSP security protocol; - ARM64 architecture; - PowerPC architecture; - RISC-V architecture; - S390 architecture; - User-Mode Linux (UML); - x86 architecture; - Block layer subsystem; - Cryptographic API; - Intel NPU Driver; - DRBD Distributed Replicated Block Device drivers; - Ublk userspace block driver; - Bluetooth drivers; - Bus devices; - Character device driver; - Clock framework and drivers; - CPU frequency scaling framework; - Hardware crypto device drivers; - EDAC drivers; - EFI core; - FWCTL subsystem; - GPU drivers; - HID subsystem; - I3C subsystem; - InfiniBand drivers; - IOMMU subsystem; - Mailbox framework; - Multiple devices driver; - Media drivers; - NVIDIA Tegra memory controller driver; - MTD block device drivers; - Network drivers; - Ethernet bonding driver; - Mellanox network drivers; - Microsoft Azure Network Adapter (MANA) driver; - STMicroelectronics network drivers; - MediaTek network drivers; - NVME drivers; - PCI subsystem; - Pin controllers subsystem; - Chrome hardware platform drivers; - ACPI WMI driver; - x86 platform drivers; - Generic PM domains; - MediaTek PM domains; - Power supply drivers; - MPAM driver; - Amlogic Meson reset controller drivers; - S/390 drivers; - SCSI subsystem; - NVIDIA Tegra Control Backbone (CBB) driver; - SPI subsystem; - Greybus lights staging drivers; - Media staging drivers; - Realtek RTL8723BS SDIO drivers; - TCM subsystem; - TTY drivers; - USB Device Class drivers; - ULPI bus; - USB Type-C support driver; - TI TPS6598x USB Power Delivery controller driver; - vDPA drivers; - VFIO drivers; - Framebuffer layer; - TSM AMD SEV Guest driver; - Xen hypervisor drivers; - File systems infrastructure; - BTRFS file system; - Ceph distributed file system; - EROFS file system; - F2FS file system; - FUSE (File system in Userspace); - GFS2 file system; - HFS+ file system; - HugeTLB file system; - Network file system (NFS) server daemon; - NILFS2 file system; - File system notification infrastructure; - NTFS3 file system; - OCFS2 file system; - Overlay file system; - Diskquota system; - SMB network file system; - Tracing file system; - DRM TTM subsystem; - Control group (cgroup); - Kernel CPU control infrastructure; - QorIQ DPAA2 FSL-MC bus driver; - Freescale ENETC Ethernet drivers; - Memory Management; - padata parallel execution mechanism; - PPP protocol drivers and compressors; - Bluetooth subsystem; - Networking core; - Netfilter; - Network traffic control; - io_uring subsystem; - IPC subsystem; - Audit subsystem; - BPF subsystem; - Kernel exit() syscall; - Kernel fork() syscall; - Kernel futex primitives; - Padata parallel execution mechanism; - Scheduler infrastructure; - Tracing infrastructure; - Cryptographic library; - Memory management; - 802.1Q VLAN protocol; - B.A.T.M.A.N. meshing protocol; - Ethernet bridge; - Ceph Core library; - Distributed Switch Architecture; - IPv4 networking; - IPv6 networking; - MAC80211 subsystem; - Multipath TCP; - Open vSwitch; - Phonet protocol; - RDS protocol; - SCTP protocol; - SMC sockets; - TIPC protocol; - TLS protocol; - Unix domain sockets; - VMware vSockets driver; - XFRM subsystem; - Integrity Measurement Architecture(IMA) framework; - SELinux security module; - ALSA framework; - HD-audio driver; - QCOM ASoC drivers; - SOF drivers; - STI ASoC drivers; - USB sound devices; - KVM subsystem; (CVE-2026-43490, CVE-2026-43492, CVE-2026-43495, CVE-2026-43496, CVE-2026-43497, CVE-2026-43498, CVE-2026-43502, CVE-2026-45834, CVE-2026-45835, CVE-2026-45836, CVE-2026-45837, CVE-2026-45838, CVE-2026-45839, CVE-2026-45840, CVE-2026-45841, CVE-2026-45842, CVE-2026-45843, CVE-2026-45844, CVE-2026-45845, CVE-2026-45846, CVE-2026-46104, CVE-2026-46105, CVE-2026-46106, CVE-2026-46107, CVE-2026-46108, CVE-2026-46109, CVE-2026-46110, CVE-2026-46111, CVE-2026-46112, CVE-2026-46113, CVE-2026-46114, CVE-2026-46116, CVE-2026-46117, CVE-2026-46118, CVE-2026-46120, CVE-2026-46121, CVE-2026-46122, CVE-2026-46123, CVE-2026-46124, CVE-2026-46125, CVE-2026-46126, CVE-2026-46127, CVE-2026-46128, CVE-2026-46129, CVE-2026-46130, CVE-2026-46131, CVE-2026-46132, CVE-2026-46133, CVE-2026-46134, CVE-2026-46136, CVE-2026-46138, CVE-2026-46139, CVE-2026-46140, CVE-2026-46141, CVE-2026-46142, CVE-2026-46143, CVE-2026-46144, CVE-2026-46145, CVE-2026-46146, CVE-2026-46147, CVE-2026-46148, CVE-2026-46149, CVE-2026-46150, CVE-2026-46151, CVE-2026-46152, CVE-2026-46153, CVE-2026-46154, CVE-2026-46156, CVE-2026-46157, CVE-2026-46158, CVE-2026-46159, CVE-2026-46160, CVE-2026-46161, CVE-2026-46162, CVE-2026-46163, CVE-2026-46164, CVE-2026-46165, CVE-2026-46166, CVE-2026-46167, CVE-2026-46168, CVE-2026-46169, CVE-2026-46170, CVE-2026-46171, CVE-2026-46172, CVE-2026-46173, CVE-2026-46174, CVE-2026-46175, CVE-2026-46176, CVE-2026-46177, CVE-2026-46178, CVE-2026-46179, CVE-2026-46180, CVE-2026-46181, CVE-2026-46182, CVE-2026-46183, CVE-2026-46184, CVE-2026-46186, CVE-2026-46187, CVE-2026-46188, CVE-2026-46189, CVE-2026-46190, CVE-2026-46191, CVE-2026-46192, CVE-2026-46193, CVE-2026-46194, CVE-2026-46196, CVE-2026-46197, CVE-2026-46198, CVE-2026-46199, CVE-2026-46200, CVE-2026-46201, CVE-2026-46202, CVE-2026-46203, CVE-2026-46204, CVE-2026-46205, CVE-2026-46206, CVE-2026-46207, CVE-2026-46208, CVE-2026-46209, CVE-2026-46210, CVE-2026-46211, CVE-2026-46212, CVE-2026-46213, CVE-2026-46214, CVE-2026-46215, CVE-2026-46216, CVE-2026-46218, CVE-2026-46219, CVE-2026-46220, CVE-2026-46221, CVE-2026-46222, CVE-2026-46223, CVE-2026-46224, CVE-2026-46225, CVE-2026-46226, CVE-2026-46227, CVE-2026-46228, CVE-2026-46229, CVE-2026-46230, CVE-2026-46231, CVE-2026-46232, CVE-2026-46233, CVE-2026-46234, CVE-2026-46235, CVE-2026-46236, CVE-2026-46238, CVE-2026-46239, CVE-2026-46240, CVE-2026-46241, CVE-2026-46242, CVE-2026-46273, CVE-2026-46274, CVE-2026-46275, CVE-2026-46290, CVE-2026-46291, CVE-2026-46292, CVE-2026-46293, CVE-2026-46294, CVE-2026-46295, CVE-2026-46296, CVE-2026-46297, CVE-2026-46298, CVE-2026-46299, CVE-2026-46301, CVE-2026-46302, CVE-2026-46303, CVE-2026-46304, CVE-2026-46305, CVE-2026-46306, CVE-2026-46307, CVE-2026-46308, CVE-2026-46309, CVE-2026-46310, CVE-2026-46311, CVE-2026-46312, CVE-2026-46313, CVE-2026-46314, CVE-2026-46315, CVE-2026-46317, CVE-2026-46318, CVE-2026-46319, CVE-2026-46320, CVE-2026-46321, CVE-2026-46322, CVE-2026-46324, CVE-2026-52911, CVE-2026-52912, CVE-2026-52913, CVE-2026-52914, CVE-2026-52915, CVE-2026-52916, CVE-2026-52918, CVE-2026-52919, CVE-2026-52920, CVE-2026-52921, CVE-2026-52922, CVE-2026-52923, CVE-2026-52925, CVE-2026-52926, CVE-2026-52927, CVE-2026-52928, CVE-2026-52931, CVE-2026-52932, CVE-2026-52934, CVE-2026-52936, CVE-2026-52937, CVE-2026-52941, CVE-2026-52943, CVE-2026-52944, CVE-2026-52949, CVE-2026-52950, CVE-2026-52951, CVE-2026-52952, CVE-2026-52953, CVE-2026-52954, CVE-2026-52955, CVE-2026-52956, CVE-2026-52957, CVE-2026-52958, CVE-2026-52959, CVE-2026-52960, CVE-2026-52961, CVE-2026-52962, CVE-2026-52963, CVE-2026-52964, CVE-2026-52965, CVE-2026-52967, CVE-2026-52968, CVE-2026-52969, CVE-2026-52970, CVE-2026-52971, CVE-2026-52973, CVE-2026-52974, CVE-2026-52975, CVE-2026-52976, CVE-2026-52977, CVE-2026-52978, CVE-2026-52979, CVE-2026-52980, CVE-2026-52981, CVE-2026-52982, CVE-2026-52983, CVE-2026-52984, CVE-2026-52985, CVE-2026-52986, CVE-2026-52987, CVE-2026-52988, CVE-2026-52989, CVE-2026-52990, CVE-2026-52991, CVE-2026-52992, CVE-2026-52993, CVE-2026-52994, CVE-2026-52995, CVE-2026-52996, CVE-2026-52997, CVE-2026-52998, CVE-2026-52999, CVE-2026-53000, CVE-2026-53001, CVE-2026-53002, CVE-2026-53003, CVE-2026-53004, CVE-2026-53005, CVE-2026-53006, CVE-2026-53007, CVE-2026-53008, CVE-2026-53009, CVE-2026-53010, CVE-2026-53011, CVE-2026-53012, CVE-2026-53013, CVE-2026-53014, CVE-2026-53015, CVE-2026-53016, CVE-2026-53017, CVE-2026-53018, CVE-2026-53019, CVE-2026-53020, CVE-2026-53021, CVE-2026-53022, CVE-2026-53023, CVE-2026-53024, CVE-2026-53025, CVE-2026-53026, CVE-2026-53027, CVE-2026-53028, CVE-2026-53029, CVE-2026-53030, CVE-2026-53031, CVE-2026-53032, CVE-2026-53033, CVE-2026-53034, CVE-2026-53035, CVE-2026-53036, CVE-2026-53037, CVE-2026-53038, CVE-2026-53039, CVE-2026-53040, CVE-2026-53041, CVE-2026-53042, CVE-2026-53043, CVE-2026-53044, CVE-2026-53045, CVE-2026-53046, CVE-2026-53047, CVE-2026-53048, CVE-2026-53049, CVE-2026-53050, CVE-2026-53051, CVE-2026-53052, CVE-2026-53053, CVE-2026-53054, CVE-2026-53055, CVE-2026-53056, CVE-2026-53057, CVE-2026-53058, CVE-2026-53059, CVE-2026-53060, CVE-2026-53061, CVE-2026-53062, CVE-2026-53063, CVE-2026-53064, CVE-2026-53065, CVE-2026-53066, CVE-2026-53067, CVE-2026-53068, CVE-2026-53069, CVE-2026-53070, CVE-2026-53071, CVE-2026-53072, CVE-2026-53073, CVE-2026-53074, CVE-2026-53075, CVE-2026-53076, CVE-2026-53077, CVE-2026-53078, CVE-2026-53079, CVE-2026-53080, CVE-2026-53081, CVE-2026-53082, CVE-2026-53083, CVE-2026-53084, CVE-2026-53085, CVE-2026-53086, CVE-2026-53087, CVE-2026-53088, CVE-2026-53089, CVE-2026-53090, CVE-2026-53091, CVE-2026-53092, CVE-2026-53093, CVE-2026-53094, CVE-2026-53095, CVE-2026-53096, CVE-2026-53097, CVE-2026-53098, CVE-2026-53099, CVE-2026-53100, CVE-2026-53101, CVE-2026-53102, CVE-2026-53103, CVE-2026-53104, CVE-2026-53105, CVE-2026-53106, CVE-2026-53107, CVE-2026-53108, CVE-2026-53109, CVE-2026-53110, CVE-2026-53111, CVE-2026-53112, CVE-2026-53113, CVE-2026-53114, CVE-2026-53115, CVE-2026-53116, CVE-2026-53117, CVE-2026-53118, CVE-2026-53119, CVE-2026-53120, CVE-2026-53121, CVE-2026-53122, CVE-2026-53123, CVE-2026-53124, CVE-2026-53125, CVE-2026-53126, CVE-2026-53127, CVE-2026-53128, CVE-2026-53129, CVE-2026-53130, CVE-2026-53174, CVE-2026-53277, CVE-2026-53278, CVE-2026-53279, CVE-2026-53280, CVE-2026-53281, CVE-2026-53282, CVE-2026-53283, CVE-2026-53284, CVE-2026-53285, CVE-2026-53286, CVE-2026-53287, CVE-2026-53288, CVE-2026-53289, CVE-2026-53290, CVE-2026-53291, CVE-2026-53292, CVE-2026-53293, CVE-2026-53294, CVE-2026-53295, CVE-2026-53296, CVE-2026-53297, CVE-2026-53298, CVE-2026-53299, CVE-2026-53300, CVE-2026-53301, CVE-2026-53302, CVE-2026-53303, CVE-2026-53304, CVE-2026-53305, CVE-2026-53306, CVE-2026-53307, CVE-2026-53308, CVE-2026-53309, CVE-2026-53310, CVE-2026-53311, CVE-2026-53312, CVE-2026-53313, CVE-2026-53314, CVE-2026-53315, CVE-2026-53316, CVE-2026-53317, CVE-2026-53318, CVE-2026-53319, CVE-2026-53320, CVE-2026-53321, CVE-2026-53322, CVE-2026-53323, CVE-2026-53324, CVE-2026-53357, CVE-2026-53358, CVE-2026-53360, CVE-2026-53364, CVE-2026-53365)
ubuntu.comJul 20, 2026extracted
USN-8507-1: Linux kernel (NVIDIA) vulnerabilities
It was discovered that some AMD processors did not properly clear data in the floating point divider unit during speculative execution. A local attacker could use this to expose sensitive information. (CVE-2025-54505) 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; - x86 architecture; - Block layer subsystem; - Cryptographic API; - Rados block device (RBD) driver; - Compressed RAM block device driver; - Character device driver; - TPM device driver; - Hardware crypto device drivers; - EDAC drivers; - GPU drivers; - Greybus drivers; - HID subsystem; - Microsoft Hyper-V drivers; - Hardware monitoring drivers; - I2C subsystem; - IIO subsystem; - InfiniBand drivers; - Input Device core drivers; - LED subsystem; - Multiple devices driver; - Media drivers; - IBM Advanced System Management driver; - MTD block device drivers; - Network drivers; - Microsoft Azure Network Adapter (MANA) driver; - NTB driver; - NVME drivers; - Device tree and open firmware driver; - PCI subsystem; - Remote Processor subsystem; - SCSI subsystem; - SPI subsystem; - Realtek RTL8723BS SDIO drivers; - SM750 framebuffer staging driver; - Thermal drivers; - USB Gadget drivers; - USB over IP driver; - VFIO drivers; - Framebuffer layer; - 9P distributed file system; - AFS file system; - Ceph distributed file system; - File systems infrastructure; - EROFS file system; - Ext4 file system; - F2FS file system; - FUSE (File system in Userspace); - Journaling layer for block devices (JBD2); - NILFS2 file system; - File system notification infrastructure; - NTFS3 file system; - OCFS2 file system; - SMB network file system; - UDF file system; - XFS file system; - Codetag library; - Memory management; - Memory Management; - KVM subsystem; - Tracing infrastructure; - User-space API (UAPI); - io_uring subsystem; - Locking primitives; - Timer subsystem; - Scatterlist API; - Heterogeneous memory management; - KASAN memory debugging framework; - Bluetooth subsystem; - Ethernet bridge; - CAIF protocol; - CAN network layer; - Ceph Core library; - IPv4 networking; - IPv6 networking; - Multipath TCP; - Netfilter; - NFC subsystem; - Packet sockets; - Qualcomm IPC Router (QRTR); - RDS protocol; - RxRPC session sockets; - SMC sockets; - Stream parser; - Landlock security; - SELinux security module; - ALSA framework; - Generic PCM loopback sound driver; - FireWire sound drivers; - Creative Sound Blaster X-Fi driver; - QCOM ASoC drivers; - USB sound devices; - Objtool; (CVE-2026-31532, CVE-2026-31574, CVE-2026-31575, CVE-2026-31576, CVE-2026-31577, CVE-2026-31578, CVE-2026-31579, CVE-2026-31580, CVE-2026-31581, CVE-2026-31582, CVE-2026-31583, CVE-2026-31584, CVE-2026-31585, CVE-2026-31586, CVE-2026-31587, CVE-2026-31588, CVE-2026-31589, CVE-2026-31590, CVE-2026-31591, CVE-2026-31592, CVE-2026-31593, CVE-2026-31594, CVE-2026-31595, CVE-2026-31596, CVE-2026-31597, CVE-2026-31598, CVE-2026-31599, CVE-2026-31600, CVE-2026-31601, CVE-2026-31602, CVE-2026-31603, CVE-2026-31604, CVE-2026-31605, CVE-2026-31606, CVE-2026-31607, CVE-2026-31608, CVE-2026-31609, CVE-2026-31610, CVE-2026-31611, CVE-2026-31612, CVE-2026-31613, CVE-2026-31614, CVE-2026-31615, CVE-2026-31616, CVE-2026-31617, CVE-2026-31618, CVE-2026-31619, CVE-2026-31620, CVE-2026-31621, CVE-2026-31622, CVE-2026-31623, CVE-2026-31624, CVE-2026-31625, CVE-2026-31626, CVE-2026-31627, CVE-2026-31628, CVE-2026-31629, CVE-2026-31686, CVE-2026-31694, CVE-2026-31696, CVE-2026-31697, CVE-2026-31698, CVE-2026-31699, CVE-2026-31700, CVE-2026-31701, CVE-2026-31702, CVE-2026-31703, CVE-2026-31704, CVE-2026-31705, CVE-2026-31706, CVE-2026-31707, CVE-2026-31708, CVE-2026-31709, CVE-2026-31710, CVE-2026-31711, CVE-2026-31712, CVE-2026-31713, CVE-2026-31714, CVE-2026-31715, CVE-2026-31716, CVE-2026-31717, CVE-2026-31718, CVE-2026-31719, CVE-2026-43058, CVE-2026-43071, CVE-2026-43072, CVE-2026-43073, CVE-2026-43348, CVE-2026-43349, CVE-2026-43350, CVE-2026-43491, CVE-2026-43493, CVE-2026-43499, CVE-2026-43501, CVE-2026-45986, CVE-2026-45987, CVE-2026-45988, CVE-2026-45989, CVE-2026-45990, CVE-2026-45991, CVE-2026-45994, CVE-2026-45995, CVE-2026-45996, CVE-2026-45997, CVE-2026-45999, CVE-2026-46001, CVE-2026-46002, CVE-2026-46003, CVE-2026-46004, CVE-2026-46005, CVE-2026-46006, CVE-2026-46007, CVE-2026-46008, CVE-2026-46009, CVE-2026-46010, CVE-2026-46011, CVE-2026-46012, CVE-2026-46013, CVE-2026-46014, CVE-2026-46015, CVE-2026-46016, CVE-2026-46018, CVE-2026-46019, CVE-2026-46020, CVE-2026-46021, CVE-2026-46022, CVE-2026-46023, CVE-2026-46024, CVE-2026-46025, CVE-2026-46026, CVE-2026-46027, CVE-2026-46028, CVE-2026-46029, CVE-2026-46030, CVE-2026-46031, CVE-2026-46032, CVE-2026-46033, CVE-2026-46034, CVE-2026-46035, CVE-2026-46036, CVE-2026-46037, CVE-2026-46038, CVE-2026-46039, CVE-2026-46040, CVE-2026-46041, CVE-2026-46042, CVE-2026-46043, CVE-2026-46044, CVE-2026-46045, CVE-2026-46046, CVE-2026-46047, CVE-2026-46049, CVE-2026-46050, CVE-2026-46051, CVE-2026-46052, CVE-2026-46053, CVE-2026-46054, CVE-2026-46056, CVE-2026-46057, CVE-2026-46058, CVE-2026-46059, CVE-2026-46060, CVE-2026-46061, CVE-2026-46062, CVE-2026-46063, CVE-2026-46064, CVE-2026-46065, CVE-2026-46066, CVE-2026-46067, CVE-2026-46068, CVE-2026-46069, CVE-2026-46070, CVE-2026-46071, CVE-2026-46072, CVE-2026-46073, CVE-2026-46074, CVE-2026-46075, CVE-2026-46076, CVE-2026-46077, CVE-2026-46078, CVE-2026-46079, CVE-2026-46080, CVE-2026-46081, CVE-2026-46082, CVE-2026-46083, CVE-2026-46084, CVE-2026-46085, CVE-2026-46086, CVE-2026-46087, CVE-2026-46088, CVE-2026-46089, CVE-2026-46090, CVE-2026-46091, CVE-2026-46092, CVE-2026-46093, CVE-2026-46094, CVE-2026-46095, CVE-2026-46096, CVE-2026-46097, CVE-2026-46098, CVE-2026-46099, CVE-2026-46100, CVE-2026-46101, CVE-2026-46102, CVE-2026-46103, CVE-2026-46115, CVE-2026-46119, CVE-2026-46135, CVE-2026-46137, CVE-2026-46155, CVE-2026-46185, CVE-2026-46195, CVE-2026-46243, CVE-2026-46244, CVE-2026-46276, CVE-2026-46277, CVE-2026-46278, CVE-2026-46279, CVE-2026-46280, CVE-2026-46281, CVE-2026-46282, CVE-2026-46283, CVE-2026-46284, CVE-2026-46285, CVE-2026-46286, CVE-2026-46287, CVE-2026-46288, CVE-2026-46289, CVE-2026-46316, CVE-2026-46332, CVE-2026-52904, CVE-2026-52905, CVE-2026-52906, CVE-2026-52907, CVE-2026-52933)
ubuntu.comJul 6, 2026extracted
USN-8488-2: Linux kernel (Raspberry Pi) vulnerabilities
It was discovered that some AMD processors did not properly clear data in the floating point divider unit during speculative execution. A local attacker could use this to expose sensitive information. (CVE-2025-54505) 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; - x86 architecture; - Block layer subsystem; - Cryptographic API; - Rados block device (RBD) driver; - Compressed RAM block device driver; - Character device driver; - TPM device driver; - Hardware crypto device drivers; - EDAC drivers; - GPU drivers; - Greybus drivers; - HID subsystem; - Microsoft Hyper-V drivers; - Hardware monitoring drivers; - I2C subsystem; - IIO subsystem; - InfiniBand drivers; - Input Device core drivers; - LED subsystem; - Multiple devices driver; - Media drivers; - IBM Advanced System Management driver; - MTD block device drivers; - Network drivers; - Microsoft Azure Network Adapter (MANA) driver; - NTB driver; - NVME drivers; - Device tree and open firmware driver; - PCI subsystem; - Remote Processor subsystem; - SCSI subsystem; - SPI subsystem; - Realtek RTL8723BS SDIO drivers; - SM750 framebuffer staging driver; - Thermal drivers; - USB Gadget drivers; - USB over IP driver; - VFIO drivers; - Framebuffer layer; - 9P distributed file system; - AFS file system; - Ceph distributed file system; - File systems infrastructure; - EROFS file system; - Ext4 file system; - F2FS file system; - FUSE (File system in Userspace); - Journaling layer for block devices (JBD2); - NILFS2 file system; - File system notification infrastructure; - NTFS3 file system; - OCFS2 file system; - SMB network file system; - UDF file system; - XFS file system; - Codetag library; - Memory management; - Memory Management; - KVM subsystem; - Tracing infrastructure; - User-space API (UAPI); - io_uring subsystem; - Locking primitives; - Timer subsystem; - Scatterlist API; - Heterogeneous memory management; - KASAN memory debugging framework; - Bluetooth subsystem; - Ethernet bridge; - CAIF protocol; - CAN network layer; - Ceph Core library; - IPv4 networking; - IPv6 networking; - Multipath TCP; - Netfilter; - NFC subsystem; - Packet sockets; - Qualcomm IPC Router (QRTR); - RDS protocol; - RxRPC session sockets; - SMC sockets; - Stream parser; - Landlock security; - SELinux security module; - ALSA framework; - Generic PCM loopback sound driver; - FireWire sound drivers; - Creative Sound Blaster X-Fi driver; - QCOM ASoC drivers; - USB sound devices; - Objtool; (CVE-2026-31532, CVE-2026-31574, CVE-2026-31575, CVE-2026-31576, CVE-2026-31577, CVE-2026-31578, CVE-2026-31579, CVE-2026-31580, CVE-2026-31581, CVE-2026-31582, CVE-2026-31583, CVE-2026-31584, CVE-2026-31585, CVE-2026-31586, CVE-2026-31587, CVE-2026-31588, CVE-2026-31589, CVE-2026-31590, CVE-2026-31591, CVE-2026-31592, CVE-2026-31593, CVE-2026-31594, CVE-2026-31595, CVE-2026-31596, CVE-2026-31597, CVE-2026-31598, CVE-2026-31599, CVE-2026-31600, CVE-2026-31601, CVE-2026-31602, CVE-2026-31603, CVE-2026-31604, CVE-2026-31605, CVE-2026-31606, CVE-2026-31607, CVE-2026-31608, CVE-2026-31609, CVE-2026-31610, CVE-2026-31611, CVE-2026-31612, CVE-2026-31613, CVE-2026-31614, CVE-2026-31615, CVE-2026-31616, CVE-2026-31617, CVE-2026-31618, CVE-2026-31619, CVE-2026-31620, CVE-2026-31621, CVE-2026-31622, CVE-2026-31623, CVE-2026-31624, CVE-2026-31625, CVE-2026-31626, CVE-2026-31627, CVE-2026-31628, CVE-2026-31629, CVE-2026-31686, CVE-2026-31694, CVE-2026-31696, CVE-2026-31697, CVE-2026-31698, CVE-2026-31699, CVE-2026-31700, CVE-2026-31701, CVE-2026-31702, CVE-2026-31703, CVE-2026-31704, CVE-2026-31705, CVE-2026-31706, CVE-2026-31707, CVE-2026-31708, CVE-2026-31709, CVE-2026-31710, CVE-2026-31711, CVE-2026-31712, CVE-2026-31713, CVE-2026-31714, CVE-2026-31715, CVE-2026-31716, CVE-2026-31717, CVE-2026-31718, CVE-2026-31719, CVE-2026-43058, CVE-2026-43071, CVE-2026-43072, CVE-2026-43073, CVE-2026-43348, CVE-2026-43349, CVE-2026-43350, CVE-2026-43491, CVE-2026-43493, CVE-2026-43499, CVE-2026-43501, CVE-2026-45986, CVE-2026-45987, CVE-2026-45988, CVE-2026-45989, CVE-2026-45990, CVE-2026-45991, CVE-2026-45994, CVE-2026-45995, CVE-2026-45996, CVE-2026-45997, CVE-2026-45999, CVE-2026-46001, CVE-2026-46002, CVE-2026-46003, CVE-2026-46004, CVE-2026-46005, CVE-2026-46006, CVE-2026-46007, CVE-2026-46008, CVE-2026-46009, CVE-2026-46010, CVE-2026-46011, CVE-2026-46012, CVE-2026-46013, CVE-2026-46014, CVE-2026-46015, CVE-2026-46016, CVE-2026-46018, CVE-2026-46019, CVE-2026-46020, CVE-2026-46021, CVE-2026-46022, CVE-2026-46023, CVE-2026-46024, CVE-2026-46025, CVE-2026-46026, CVE-2026-46027, CVE-2026-46028, CVE-2026-46029, CVE-2026-46030, CVE-2026-46031, CVE-2026-46032, CVE-2026-46033, CVE-2026-46034, CVE-2026-46035, CVE-2026-46036, CVE-2026-46037, CVE-2026-46038, CVE-2026-46039, CVE-2026-46040, CVE-2026-46041, CVE-2026-46042, CVE-2026-46043, CVE-2026-46044, CVE-2026-46045, CVE-2026-46046, CVE-2026-46047, CVE-2026-46049, CVE-2026-46050, CVE-2026-46051, CVE-2026-46052, CVE-2026-46053, CVE-2026-46054, CVE-2026-46056, CVE-2026-46057, CVE-2026-46058, CVE-2026-46059, CVE-2026-46060, CVE-2026-46061, CVE-2026-46062, CVE-2026-46063, CVE-2026-46064, CVE-2026-46065, CVE-2026-46066, CVE-2026-46067, CVE-2026-46068, CVE-2026-46069, CVE-2026-46070, CVE-2026-46071, CVE-2026-46072, CVE-2026-46073, CVE-2026-46074, CVE-2026-46075, CVE-2026-46076, CVE-2026-46077, CVE-2026-46078, CVE-2026-46079, CVE-2026-46080, CVE-2026-46081, CVE-2026-46082, CVE-2026-46083, CVE-2026-46084, CVE-2026-46085, CVE-2026-46086, CVE-2026-46087, CVE-2026-46088, CVE-2026-46089, CVE-2026-46090, CVE-2026-46091, CVE-2026-46092, CVE-2026-46093, CVE-2026-46094, CVE-2026-46095, CVE-2026-46096, CVE-2026-46097, CVE-2026-46098, CVE-2026-46099, CVE-2026-46100, CVE-2026-46101, CVE-2026-46102, CVE-2026-46103, CVE-2026-46115, CVE-2026-46119, CVE-2026-46135, CVE-2026-46137, CVE-2026-46155, CVE-2026-46185, CVE-2026-46195, CVE-2026-46243, CVE-2026-46244, CVE-2026-46276, CVE-2026-46277, CVE-2026-46278, CVE-2026-46279, CVE-2026-46280, CVE-2026-46281, CVE-2026-46282, CVE-2026-46283, CVE-2026-46284, CVE-2026-46285, CVE-2026-46286, CVE-2026-46287, CVE-2026-46288, CVE-2026-46289, CVE-2026-46316, CVE-2026-46332, CVE-2026-52904, CVE-2026-52905, CVE-2026-52906, CVE-2026-52907, CVE-2026-52933)
ubuntu.comJul 2, 2026extracted
USN-8488-1: Linux kernel vulnerabilities
It was discovered that some AMD processors did not properly clear data in the floating point divider unit during speculative execution. A local attacker could use this to expose sensitive information. (CVE-2025-54505) 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; - x86 architecture; - Block layer subsystem; - Cryptographic API; - Rados block device (RBD) driver; - Compressed RAM block device driver; - Character device driver; - TPM device driver; - Hardware crypto device drivers; - EDAC drivers; - GPU drivers; - Greybus drivers; - HID subsystem; - Microsoft Hyper-V drivers; - Hardware monitoring drivers; - I2C subsystem; - IIO subsystem; - InfiniBand drivers; - Input Device core drivers; - LED subsystem; - Multiple devices driver; - Media drivers; - IBM Advanced System Management driver; - MTD block device drivers; - Network drivers; - Microsoft Azure Network Adapter (MANA) driver; - NTB driver; - NVME drivers; - Device tree and open firmware driver; - PCI subsystem; - Remote Processor subsystem; - SCSI subsystem; - SPI subsystem; - Realtek RTL8723BS SDIO drivers; - SM750 framebuffer staging driver; - Thermal drivers; - USB Gadget drivers; - USB over IP driver; - VFIO drivers; - Framebuffer layer; - 9P distributed file system; - AFS file system; - Ceph distributed file system; - File systems infrastructure; - EROFS file system; - Ext4 file system; - F2FS file system; - FUSE (File system in Userspace); - Journaling layer for block devices (JBD2); - NILFS2 file system; - File system notification infrastructure; - NTFS3 file system; - OCFS2 file system; - SMB network file system; - UDF file system; - XFS file system; - Codetag library; - Memory management; - Memory Management; - KVM subsystem; - Tracing infrastructure; - User-space API (UAPI); - io_uring subsystem; - Locking primitives; - Timer subsystem; - Scatterlist API; - Heterogeneous memory management; - KASAN memory debugging framework; - Bluetooth subsystem; - Ethernet bridge; - CAIF protocol; - CAN network layer; - Ceph Core library; - IPv4 networking; - IPv6 networking; - Multipath TCP; - Netfilter; - NFC subsystem; - Packet sockets; - Qualcomm IPC Router (QRTR); - RDS protocol; - RxRPC session sockets; - SMC sockets; - Stream parser; - Landlock security; - SELinux security module; - ALSA framework; - Generic PCM loopback sound driver; - FireWire sound drivers; - Creative Sound Blaster X-Fi driver; - QCOM ASoC drivers; - USB sound devices; - Objtool; (CVE-2026-31532, CVE-2026-31574, CVE-2026-31575, CVE-2026-31576, CVE-2026-31577, CVE-2026-31578, CVE-2026-31579, CVE-2026-31580, CVE-2026-31581, CVE-2026-31582, CVE-2026-31583, CVE-2026-31584, CVE-2026-31585, CVE-2026-31586, CVE-2026-31587, CVE-2026-31588, CVE-2026-31589, CVE-2026-31590, CVE-2026-31591, CVE-2026-31592, CVE-2026-31593, CVE-2026-31594, CVE-2026-31595, CVE-2026-31596, CVE-2026-31597, CVE-2026-31598, CVE-2026-31599, CVE-2026-31600, CVE-2026-31601, CVE-2026-31602, CVE-2026-31603, CVE-2026-31604, CVE-2026-31605, CVE-2026-31606, CVE-2026-31607, CVE-2026-31608, CVE-2026-31609, CVE-2026-31610, CVE-2026-31611, CVE-2026-31612, CVE-2026-31613, CVE-2026-31614, CVE-2026-31615, CVE-2026-31616, CVE-2026-31617, CVE-2026-31618, CVE-2026-31619, CVE-2026-31620, CVE-2026-31621, CVE-2026-31622, CVE-2026-31623, CVE-2026-31624, CVE-2026-31625, CVE-2026-31626, CVE-2026-31627, CVE-2026-31628, CVE-2026-31629, CVE-2026-31686, CVE-2026-31694, CVE-2026-31696, CVE-2026-31697, CVE-2026-31698, CVE-2026-31699, CVE-2026-31700, CVE-2026-31701, CVE-2026-31702, CVE-2026-31703, CVE-2026-31704, CVE-2026-31705, CVE-2026-31706, CVE-2026-31707, CVE-2026-31708, CVE-2026-31709, CVE-2026-31710, CVE-2026-31711, CVE-2026-31712, CVE-2026-31713, CVE-2026-31714, CVE-2026-31715, CVE-2026-31716, CVE-2026-31717, CVE-2026-31718, CVE-2026-31719, CVE-2026-43058, CVE-2026-43071, CVE-2026-43072, CVE-2026-43073, CVE-2026-43348, CVE-2026-43349, CVE-2026-43350, CVE-2026-43491, CVE-2026-43493, CVE-2026-43499, CVE-2026-43501, CVE-2026-45986, CVE-2026-45987, CVE-2026-45988, CVE-2026-45989, CVE-2026-45990, CVE-2026-45991, CVE-2026-45994, CVE-2026-45995, CVE-2026-45996, CVE-2026-45997, CVE-2026-45999, CVE-2026-46001, CVE-2026-46002, CVE-2026-46003, CVE-2026-46004, CVE-2026-46005, CVE-2026-46006, CVE-2026-46007, CVE-2026-46008, CVE-2026-46009, CVE-2026-46010, CVE-2026-46011, CVE-2026-46012, CVE-2026-46013, CVE-2026-46014, CVE-2026-46015, CVE-2026-46016, CVE-2026-46018, CVE-2026-46019, CVE-2026-46020, CVE-2026-46021, CVE-2026-46022, CVE-2026-46023, CVE-2026-46024, CVE-2026-46025, CVE-2026-46026, CVE-2026-46027, CVE-2026-46028, CVE-2026-46029, CVE-2026-46030, CVE-2026-46031, CVE-2026-46032, CVE-2026-46033, CVE-2026-46034, CVE-2026-46035, CVE-2026-46036, CVE-2026-46037, CVE-2026-46038, CVE-2026-46039, CVE-2026-46040, CVE-2026-46041, CVE-2026-46042, CVE-2026-46043, CVE-2026-46044, CVE-2026-46045, CVE-2026-46046, CVE-2026-46047, CVE-2026-46049, CVE-2026-46050, CVE-2026-46051, CVE-2026-46052, CVE-2026-46053, CVE-2026-46054, CVE-2026-46056, CVE-2026-46057, CVE-2026-46058, CVE-2026-46059, CVE-2026-46060, CVE-2026-46061, CVE-2026-46062, CVE-2026-46063, CVE-2026-46064, CVE-2026-46065, CVE-2026-46066, CVE-2026-46067, CVE-2026-46068, CVE-2026-46069, CVE-2026-46070, CVE-2026-46071, CVE-2026-46072, CVE-2026-46073, CVE-2026-46074, CVE-2026-46075, CVE-2026-46076, CVE-2026-46077, CVE-2026-46078, CVE-2026-46079, CVE-2026-46080, CVE-2026-46081, CVE-2026-46082, CVE-2026-46083, CVE-2026-46084, CVE-2026-46085, CVE-2026-46086, CVE-2026-46087, CVE-2026-46088, CVE-2026-46089, CVE-2026-46090, CVE-2026-46091, CVE-2026-46092, CVE-2026-46093, CVE-2026-46094, CVE-2026-46095, CVE-2026-46096, CVE-2026-46097, CVE-2026-46098, CVE-2026-46099, CVE-2026-46100, CVE-2026-46101, CVE-2026-46102, CVE-2026-46103, CVE-2026-46115, CVE-2026-46119, CVE-2026-46135, CVE-2026-46137, CVE-2026-46155, CVE-2026-46185, CVE-2026-46195, CVE-2026-46243, CVE-2026-46244, CVE-2026-46276, CVE-2026-46277, CVE-2026-46278, CVE-2026-46279, CVE-2026-46280, CVE-2026-46281, CVE-2026-46282, CVE-2026-46283, CVE-2026-46284, CVE-2026-46285, CVE-2026-46286, CVE-2026-46287, CVE-2026-46288, CVE-2026-46289, CVE-2026-46316, CVE-2026-46332, CVE-2026-52904, CVE-2026-52905, CVE-2026-52906, CVE-2026-52907, CVE-2026-52933)
ubuntu.comJul 1, 2026extracted
USN-8489-1: Linux kernel (OEM) vulnerabilities
It was discovered that the Linux kernel did not properly handle shared page fragments during socket buffer operations, collectively known as Dirty Frag. A logic flaw existed in the XFRM ESP-in-TCP subsystem and in the RxRPC networking subsystem when processing paged fragments. A local attacker could use this to escalate privileges, or possibly escape a container. (CVE-2026-43284, CVE-2026-43500, CVE-2026-45998, CVE-2026-46000) It was discovered that a logic flaw existed in the XFRM ESP-in-TCP subsystem in the Linux kernel when handling socket buffer fragments. This flaw is known as Fragnesia. A local attacker could use this to escalate privileges, or possibly escape a container. (CVE-2026-43503, CVE-2026-46300) Qualys discovered that a race condition existed in the ptrace subsystem of the Linux kernel when privileged processes are exiting. An unprivileged local attacker could use this issue to expose sensitive information. (CVE-2026-46333) Tristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0 contain a memory leak when handling AppArmor notifications. A local attacker could use this to cause resource exhaustion. (CVE-2026-47326) Tristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0 contain a NULL pointer dereference when handling AppArmor notifications. A local attacker could use this to cause a kernel oops. (CVE-2026-47327) Tristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0 contained an invalid free when handling AppArmor notifications. A local attacker could use this to corrupt kernel memory. (CVE-2026-47328) Tristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0 contained insufficient validation of AppArmor notification responses. A local attacker could use this to allow crafted responses to be processed. (CVE-2026-47329) Tristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0 used an uninitialized variable when handling AppArmor notifications. A local attacker could use this to cause incorrect caching of data. (CVE-2026-47330) Tristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0 contained an out-of-bounds (OOB) read when handling AppArmor notifications. A local attacker could use this to cause information disclosure of kernel memory. (CVE-2026-47332) Tristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0 contained a out-of-bounds (OOB) read when handling AppArmor notifications. A local attacker could use this to cause kernel memory corruption and, theoretically, influence processing of AppArmor policies. (CVE-2026-47333) Tristan Madani discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0 contained incorrect holding of locks when handling AppArmor notifications. A local attacker could use this to cause a kernel panic or deadlock. (CVE-2026-47334) Tristan Madani and Trevor Lawrence have each independently discovered that Ubuntu Linux kernel 6.8, 6.17 and 7.0 contained a NULL pointer dereference when handling AppArmor network socket mediation. A local attacker could use this to cause a kernel oops. (CVE-2026-47337) 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; - x86 architecture; - Block layer subsystem; - Cryptographic API; - Rados block device (RBD) driver; - Compressed RAM block device driver; - Character device driver; - TPM device driver; - Hardware crypto device drivers; - EDAC drivers; - GPU drivers; - Greybus drivers; - Hardware monitoring drivers; - IIO subsystem; - InfiniBand drivers; - Input Device core drivers; - LED subsystem; - Multiple devices driver; - Media drivers; - IBM Advanced System Management driver; - MTD block device drivers; - Network drivers; - Microsoft Azure Network Adapter (MANA) driver; - NVME drivers; - Device tree and open firmware driver; - PCI subsystem; - Remote Processor subsystem; - SCSI subsystem; - SPI subsystem; - Thermal drivers; - VFIO drivers; - Framebuffer layer; - 9P distributed file system; - AFS file system; - Ceph distributed file system; - EROFS file system; - File systems infrastructure; - Ext4 file system; - Journaling layer for block devices (JBD2); - File system notification infrastructure; - NTFS3 file system; - OCFS2 file system; - Overlay file system; - SMB network file system; - UDF file system; - XFS file system; - Codetag library; - Memory management; - Tracing infrastructure; - io_uring subsystem; - Locking primitives; - Scatterlist API; - Heterogeneous memory management; - Bluetooth subsystem; - Ethernet bridge; - CAIF protocol; - Ceph Core library; - Networking core; - IPv4 networking; - IPv6 networking; - Multipath TCP; - Netfilter; - Qualcomm IPC Router (QRTR); - RDS protocol; - RxRPC session sockets; - SMC sockets; - Stream parser; - Landlock security; - SELinux security module; - ALSA framework; - Generic PCM loopback sound driver; - Creative Sound Blaster X-Fi driver; - USB sound devices; (CVE-2026-43491, CVE-2026-43493, CVE-2026-43494, CVE-2026-43499, CVE-2026-43501, CVE-2026-45986, CVE-2026-45987, CVE-2026-45988, CVE-2026-45989, CVE-2026-45990, CVE-2026-45991, CVE-2026-45994, CVE-2026-45995, CVE-2026-45996, CVE-2026-45997, CVE-2026-45999, CVE-2026-46001, CVE-2026-46002, CVE-2026-46003, CVE-2026-46004, CVE-2026-46005, CVE-2026-46006, CVE-2026-46007, CVE-2026-46008, CVE-2026-46009, CVE-2026-46010, CVE-2026-46011, CVE-2026-46012, CVE-2026-46013, CVE-2026-46014, CVE-2026-46015, CVE-2026-46016, CVE-2026-46018, CVE-2026-46019, CVE-2026-46020, CVE-2026-46021, CVE-2026-46022, CVE-2026-46023, CVE-2026-46024, CVE-2026-46025, CVE-2026-46026, CVE-2026-46027, CVE-2026-46028, CVE-2026-46029, CVE-2026-46030, CVE-2026-46031, CVE-2026-46032, CVE-2026-46033, CVE-2026-46034, CVE-2026-46035, CVE-2026-46036, CVE-2026-46037, CVE-2026-46038, CVE-2026-46039, CVE-2026-46040, CVE-2026-46041, CVE-2026-46042, CVE-2026-46043, CVE-2026-46044, CVE-2026-46045, CVE-2026-46046, CVE-2026-46047, CVE-2026-46048, CVE-2026-46049, CVE-2026-46050, CVE-2026-46051, CVE-2026-46052, CVE-2026-46053, CVE-2026-46054, CVE-2026-46056, CVE-2026-46057, CVE-2026-46058, CVE-2026-46059, CVE-2026-46060, CVE-2026-46061, CVE-2026-46062, CVE-2026-46063, CVE-2026-46064, CVE-2026-46065, CVE-2026-46066, CVE-2026-46067, CVE-2026-46068, CVE-2026-46069, CVE-2026-46070, CVE-2026-46071, CVE-2026-46072, CVE-2026-46073, CVE-2026-46074, CVE-2026-46075, CVE-2026-46076, CVE-2026-46077, CVE-2026-46078, CVE-2026-46079, CVE-2026-46080, CVE-2026-46081, CVE-2026-46082, CVE-2026-46083, CVE-2026-46084, CVE-2026-46085, CVE-2026-46086, CVE-2026-46087, CVE-2026-46088, CVE-2026-46089, CVE-2026-46090, CVE-2026-46091, CVE-2026-46092, CVE-2026-46093, CVE-2026-46094, CVE-2026-46095, CVE-2026-46096, CVE-2026-46097, CVE-2026-46098, CVE-2026-46099, CVE-2026-46100, CVE-2026-46101, CVE-2026-46102, CVE-2026-46103, CVE-2026-46115, CVE-2026-46119, CVE-2026-46135, CVE-2026-46137, CVE-2026-46155, CVE-2026-46185, CVE-2026-46195, CVE-2026-46243, CVE-2026-46244, CVE-2026-46276, CVE-2026-46277, CVE-2026-46278, CVE-2026-46279, CVE-2026-46280, CVE-2026-46281, CVE-2026-46282, CVE-2026-46283, CVE-2026-46284, CVE-2026-46285, CVE-2026-46286, CVE-2026-46287, CVE-2026-46288, CVE-2026-46289, CVE-2026-46316, CVE-2026-46323, CVE-2026-46332, CVE-2026-52904, CVE-2026-52905, CVE-2026-52906, CVE-2026-52907, CVE-2026-52933, CVE-2026-53174)
ubuntu.comJul 1, 2026extracted
Vulnerability Research: scoperti 7 Gap di Hardening nelle Variabili d’Ambiente di env.c in sudo
Nel corso di un audit indipendente del modulo plugins/sudoers/env.c in sudo 1.9.17p2 / 1.9.18rc1, sono state identificate sette variabili d’ambiente che vengono trasmesse ai processi privilegiati quando env_reset è disabilitato (!env_reset in sudoers) o quando il flag -E viene usato per preservare l’ambiente (sudo -E). Queste variabili — NODE_OPTIONS, NODE_PATH, GIT_SSH_COMMAND, _JAVA_OPTIONS, CLASSPATH, GIT_CONFIG_GLOBAL e PYTHONSTARTUP — non sono presenti nelle blacklist initial_badenv_table o badenv_table di sudo, e ciascuna fornisce un primitivo di esecuzione di codice ben documentato per il runtime corrispondente. Questa ricerca è classificata come gap di hardening piuttosto che come una vulnerabilità classica. La causa radice non è un difetto nella logica core di sudo — env_reset funziona correttamente per design. Il gap risiede nella completezza della deny-list: man mano che l’ecosistema dei runtime interpretati (Node.js, Python, JVM, Git) è cresciuto nel tempo, la blacklist non è mai stata aggiornata per tenere conto dei loro primitivi di injection a livello di variabili d’ambiente. Il maintainer upstream Todd C. Miller ha riconosciuto i finding e committato un fix in plugins/sudoers/env.c. Nessun CVE è stato richiesto, coerentemente con il framing del maintainer della modifica come un miglioramento di hardening alla deny-list. Classificazione: Gap di Hardening — Local Privilege Escalation CWE: CWE-269 (Improper Privilege Management) Versioni affette: sudo ≤ 1.9.17p2, 1.9.18rc1 Condizioni di esposizione: Defaults !env_reset in sudoers, oppure sudo -E dove SETENV è esplicitamente concesso Motivazione e Perimetro L’idea è nata da una domanda semplice: *”sudo sanitizza davvero ogni variabile d’ambiente pericolosa?”* Il file env.c nel plugin sudoers è stato rafforzato nel corso degli anni — LD_PRELOAD, LD_LIBRARY_PATH, SHELLOPTS, PERL5OPT e molte altre sono correttamente in blacklist. Ma l’ecosistema dei runtime si è espanso enormemente da quando quelle liste sono state scritte. Node.js, Python, JVM e Git espongono ciascuno la propria superficie di injection a livello di variabili d’ambiente, e nessuno di loro era sul radar di sudo. Metodologia L’approccio: enumerare ogni runtime che sudo potrebbe invocare in un contesto DevOps (Node.js, Python, JVM, Git), poi incrociare le loro variabili d’ambiente documentate per l’esecuzione di codice con le blacklist esistenti. L’audit ha coperto anche la logica env_should_delete() di sudo, che applica pattern di corrispondenza esatta e glob con prefisso. Le variabili che sfruttano runtime non contemplati nella lista originale non hanno pattern corrispondente in nessuna delle due tabelle. Strumenti utilizzati: grep ,cscope per la navigazione rapida del codebase Semgrep con regole custom per rilevare percorsi di pass-through delle variabili d’ambiente Trace manuale delle call chain env_init() →env_should_delete() →env_update_didvar() Fase 2 — Validazione Dinamica (DAST / Docker Lab) Ogni variabile candidata è stata validata in un Docker lab isolato per eliminare i falsi positivi — un passaggio critico, poiché non tutti i candidati SAST si traducono in exploitability reale. Sono state testate in parallelo due configurazioni del lab: una con !env_reset esplicito (non-default ma comune in ambito enterprise), e una che simula il sudoers di default di Ubuntu con sudo -E — il finding più significativo dal punto di vista della superficie d’attacco reale. Architettura del lab: ┌──────────────────────────────────────────────────────────┐│ Docker Compose Lab — due configurazioni ││ ││ ┌─────────────────────────┐ ┌───────────────────────┐ ││ │ victim-A │ │ victim-B │ ││ │ sudo 1.9.17p2 │ │ sudo 1.9.17p2 │ ││ │ Defaults !env_reset │ │ Ubuntu default │ ││ │ NOPASSWD:ALL │ │ %sudo ALL=(ALL:ALL) │ ││ │ (config non-default) │ │ ALL (no NOSETENV) │ ││ └─────────────────────────┘ └───────────────────────┘ ││ ││ Test A: export VAR=payload; sudo ││ Test B: export VAR=payload; sudo -E ││ Atteso: esecuzione di codice come root? │└──────────────────────────────────────────────────────────┘ Snippet sudoers Docker utilizzati per la validazione: victim-A — !env_reset esplicito (non-default)Defaults !env_resettestuser ALL=(ALL) NOPASSWD: ALL# victim-B — simulazione Ubuntu default (senza NOSETENV)%sudo ALL=(ALL:ALL) AL Ogni test ha seguito un template exploit standard, eseguito su entrambe le configurazioni: Template utilizzato per ogni findingexport =" "# Test A — !env_resetsudo # Test B — Ubuntu default + sudo -Esudo -E # Atteso: shell root o esecuzione di codice arbitrario in entrambi i cas Fase 3 — Disclosure Coordinata Tutti i finding confermati sono stati raccolti in un’email di disclosure strutturata e inviata a Todd C. Miller ([email protected]) seguendo le linee guida di responsible disclosure del progetto. L’email completa e la risposta upstream sono documentate nella Sezione 5. I Sette Finding Ogni finding è presentato con: nome della variabile, runtime affetto, meccanismo di exploit preciso, comando PoC validato nel Docker lab, e conferma del bypass su entrambe le configurazioni !env_reset e sudo -E. Finding #1 — NODE_OPTIONS (Code Injection nel Runtime Node.js) Variabile: NODE_OPTIONS Runtime: Node.js Meccanismo: Node.js elabora questa variabile come se i flag fossero passati da riga di comando. Il flag –require causa il caricamento di un modulo arbitrario prima che qualsiasi script venga eseguito — inclusi gli script in esecuzione come root. PoC: Crea il modulo malevolocat > /tmp/evil.js /tmp/pwned && chmod 777 /tmp/pwned');EOFexport NODE_OPTIONS="--require /tmp/evil.js"sudo node -e "console.log('script legittimo')"# Risultato: /tmp/pwned contiene "uid=0(root) gid=0(root)..." Severity (gap di hardening): Impatto critico se innescato — esecuzione di codice arbitrario come root Nota: Funziona anche con --require=/tmp/evil.js, --import e --env-file nelle versioni più recenti di Node.js. Finding #2 — NODE_PATH (Hijacking del Modulo Node.js) Variabile: NODE_PATH Runtime: Node.js Meccanismo: Node.js antepone le directory in NODE_PATH al percorso di ricerca dei moduli. Un override malevolo di require('fs') posizionato in una directory controllata dall’attaccante sostituirà il modulo built-in. PoC: mkdir -p /tmp/evil_modulescat > /tmp/evil_modules/path.js /tmp/git_ssh_pwned; ssh \\$*' --"sudo git ls-remote [email protected]:user/repo.git /tmp/tes Severity (gap di hardening): Alta Nota: Richiede che il comando git privilegiato contatti un remote SSH. Scenario altamente realistico in ambienti CI/CD. Finding #4 — _JAVA_OPTIONS (Injection di Agent JVM Arbitrario) Variabile: _JAVA_OPTIONS Runtime: Java (OpenJDK, Oracle JDK) Meccanismo: La JVM legge _JAVA_OPTIONS e ne antepone il contenuto agli argomenti da riga di comando prima di qualsiasi flag fornito dall’utente. Il flag -javaagent consente di caricare un Java Agent arbitrario (JAR) che viene eseguito con il livello di privilegio della JVM — ovvero, root. PoC: (Richiede un evil-agent.jar compilato — incluso nel lab)export _JAVA_OPTIONS="-javaagent:/tmp/evil-agent.jar"sudo java -jar /opt/app-legittima.ja Severity (gap di hardening): Alta Nota: JAVA_TOOL_OPTIONS presenta un comportamento identico e dovrebbe essere considerata per lo stesso fix. Finding #5 — CLASSPATH (Hijacking del Classpath Java) Variabile: CLASSPATH Runtime: Java Meccanismo: Anteponendo una directory controllata dall’attaccante a CLASSPATH, è possibile sostituire qualsiasi classe caricata dalla JVM prima che le entry del classpath dell’applicazione vengano cercate. Combinato con un’invocazione privilegiata di sudo java, si ottiene esecuzione di codice arbitrario. PoC: mkdir -p /tmp/evil_cp# Compila una sostituzione malevola di una classe usata dall'applicazione# (es. com/example/Config.class)export CLASSPATH="/tmp/evil_cp:$CLASSPATH"sudo java com.example.App Severity (gap di hardening): Media (richiede la conoscenza di una classe caricata all'avvio dall'applicazione target) Finding #6 — GIT_CONFIG_GLOBAL (Override di Configurazione Git Arbitraria) Variabile: GIT_CONFIG_GLOBAL Runtime: Git Meccanismo: Git legge il file puntato da GIT_CONFIG_GLOBAL come configurazione Git a livello utente, sovrascrivendo ~/.gitconfig. Un file di configurazione controllato dall’attaccante può ridefinire core.sshCommand per redirezionare le operazioni SSH di Git attraverso un binario arbitrario. PoC: cat > /tmp/evil.gitconfig /tmp/git_cfg_pwned; ssh $*' --EOFexport GIT_CONFIG_GLOBAL="/tmp/evil.gitconfig"sudo git ls-remote [email protected]:user/repo.git /tmp/cfg-tes Severity (gap di hardening): Alta Nota: Più stealthy di GIT_SSH_COMMAND — il payload è offloaded in un file esterno che potrebbe non essere ispezionato dai defender. Finding #7 — PYTHONSTARTUP (Esecuzione di Codice Arbitrario all’Avvio di Python) Variabile: PYTHONSTARTUP Runtime: CPython Meccanismo: Quando Python avvia una sessione interattiva, legge ed esegue il file puntato da PYTHONSTARTUP prima della REPL o di qualsiasi script. La variabile è rispettata solo in modalità interattiva, ma molti strumenti di amministrazione reali invocano Python interattivamente per task di manutenzione. PoC: cat > /tmp/evil_startup.py /tmp/python_startup_pwned')EOFexport PYTHONSTARTUP="/tmp/evil_startup.py"sudo python3 # sessione interattiva → payload eseguito come roo Severity (gap di hardening): Media Nota: Python 3.x rispetta anche PYTHONSAFEPATH=0 e PYTHONINSPECT, che sono stati analizzati e risultano varianti a severity inferiore non incluse in questa submission. Falsi Positivi Corretti Durante la Ricerca Un processo disciplinato di validazione in lab è importante quanto la scoperta statica iniziale. Diverse variabili identificate nella Fase 1 sono state scartate dopo i test Docker: Eliminare questi finding prima della disclosure mantiene la credibilità del report e rispetta il tempo del maintainer. Responsible Disclosure — Comunicazione con Todd Miller In data 2026-03-16, ho contattato Todd C. Miller, autore originale e maintainer di sudo, all’indirizzo [email protected] con il seguente riepilogo: I am a cybersecurity researcher based in Italy. During a source code review of sudo’s environment handling (plugins/sudoers/env.c), identified 7 environment variables that are not present in the initial_badenv_table and can lead to arbitrary code execution when env_reset is disabled (Defaults !env_reset). Variabili affette:NODE_OPTIONS, NODE_PATH, GIT_SSH_COMMAND, _JAVA_OPTIONS, CLASSPATH, GIT_CONFIG_GLOBAL, PYTHONSTARTUP Each variable provides a code execution primitive for the corresponding runtime. Full technical details, PoC commands, and instructions for the Docker lab are attached. I am available to coordinate the timing of any fix release with the publication of my blog post. Best regards, Michele Piccinni 5.1 Risposta di Todd C. Miller Todd ha risposto in modo tempestivo e costruttivo. La risposta completa: Da: Todd C. Miller Hi Michele, Thank you for notifying me about this. While the default is to reset the environment for commands run by sudo, I agree that it is worth adding those variables to the list that are removed when “env_reset” is disabled, or when “sudo -E” is used to preserve the environment. Would like you me to wait until you have published your article is published before the changes are committed? Con questa risposta si chiude il processo di vulnerability disclosure: Todd ha riconosciuto la validità di tutti e sette i finding senza contestazioni. Ha inquadrato il fix esplicitamente come un miglioramento alla deny-list in condizioni non-default — “worth adding” — che è il linguaggio di una modifica di hardening, non di una patch di vulnerabilità. Questo è coerente con la posizione del progetto: env_reset è il controllo primario corretto, e la deny-list è uno strato di defence-in-depth. Ha rimandato alla mia timeline di pubblicazione — un gesto di rispetto professionale purtroppo raro nel mondo della disclosure. Significativamente, Todd non ha menzionato coordinamento CVE, periodi di embargo o notifiche alle distro — confermando che questo è trattato upstream come un miglioramento di hardening piuttosto che un difetto CVE-eligible. Il Fix Upstream A seguito della disclosure coordinata, Todd C. Miller ha committato il fix nel repository ufficiale sudo-project/sudo. Commit: 40217ea Release: sudo 1.9.18 Reported by: Michele Piccinni Il messaggio di commit ufficiale recita testualmente: Additional variables for initial_badenv_table[] Adds NODE_OPTIONS, NODE_PATH, _JAVA_OPTIONS, CLASSPATH, GIT_SSH_COMMAND, GIT_CONFIG_GLOBAL, and PYTHONSTARTUP to the list of variables to remove from the environment when “env_reset” is disabled, or sudo’s “-E” option is used (if allowed by sudoers). From Michele Piccinni. Il fix aggiunge tutte e sette le variabili direttamente a initial_badenv_table[] in plugins/sudoers/env.c, applicato incondizionatamente ogni volta che la logica della deny-list viene eseguita — coprendo sia il percorso !env_reset che il percorso sudo -E con una singola modifica. /* plugins/sudoers/env.c — fix upstream (Todd C. Miller) */static const char *initial_badenv_table[] = { /* ... entry esistenti ... */ "NODE_OPTIONS", /* Node.js: --require/--import arbitrario */ "NODE_PATH", /* Node.js: hijack percorso moduli */ "GIT_SSH_COMMAND", /* Git: command injection SSH */ "_JAVA_OPTIONS", /* JVM: -javaagent arbitrario */ "CLASSPATH", /* Java: hijack classpath */ "GIT_CONFIG_GLOBAL", /* Git: override config arbitrario */ "PYTHONSTARTUP", /* Python: esecuzione script all'avvio */ NULL}; Per l’implementazione autorevole fare riferimento al diff del commit su GitHub. Valutazione dell’Impatto e Configurazioni Affette Il caso Ubuntu merita attenzione particolare. La regola sudoers di default: %sudo ALL=(ALL:ALL) ALL non include NOSETENV, il che secondo la policy di sudo significa che SETENV è implicitamente permesso. Qualsiasi utente nel gruppo sudo può quindi eseguire sudo -E e avere il proprio ambiente completo — incluse tutte e sette le variabili pericolose — trasmesso al processo privilegiato. Questa è una configurazione che l’utente e l’amministratore Ubuntu medio non considererebbe non-default o non sicura. La causa radice si riassume in meccanismi ben progettati (env_reset, badenv_table) diventano incompleti man mano che il panorama delle minacce evolve. La deny-list è stata scritta prima che Node.js, Git moderno e il tooling JVM diventassero onnipresenti in contesti privilegiati. Remediation Verifica se il tuo sistema è esposto: Verifica se sudo -E è permesso senza SETENV esplicito nel sudoerssudo -V | grep -i setenv# Controlla la policy sudoers effettiva per SETENV/NOSETENVsudo -l | grep -i setenv# Test rapido di esposizione (eseguire come membro non-root del gruppo sudo)export NODE_OPTIONS="--version"sudo -E node 2>/dev/null && echo "ESPOSTO: sudo -E passa NODE_OPTIONS" \ || echo "Protetto" Azione immediata: Aggiornare sudo alla versione patchata non appena disponibile nei repository della propria distribuzione. Ubuntu / Debiansudo apt update && sudo apt upgrade sudo# RHEL / Fedora / Rockysudo dnf update sudo# Verifica versionesudo --version Hardening temporaneo (se la patch non è ancora disponibile): Rimuovere !env_reset da/etc/sudoers se non strettamente necessario. Verificare i grant SETENV /sudo -E e revocarli dove possibile. Aggiungere entry env_delete manuali al sudoers come soluzione temporanea:Defaults env_delete += "NODE_OPTIONS NODE_PATH GIT_SSH_COMMAND" Defaults env_delete += "_JAVA_OPTIONS CLASSPATH GIT_CONFIG_GLOBAL PYTHONSTARTUP" Abilitare profili AppArmor/SELinux per i comandi sudo con accesso ristretto. Conclusioni Questa ricerca illustra un pattern ricorrente nella sicurezza: meccanismi ben progettati (env_reset, badenv_table) diventano incompleti man mano che il panorama delle minacce evolve. La deny-list in env.c non è mai stata aggiornata per tenere conto dei primitivi di injection a livello di variabili d’ambiente di Node.js, Python, JVM e Git — runtime oggi onnipresenti in contesti DevOps privilegiati. Sulla correttezza della classificazione. Questi finding sono correttamente classificati come gap di hardening, non come vulnerabilità in senso tradizionale. Il maintainer upstream ha concordato, e la sua risposta lo riflette. Un ricercatore che gonfia i finding in CVE che non riesce a sostenere perde credibilità molto più rapidamente di chi pubblica ricerca di hardening accurata e tecnicamente rigorosa. Il commit nel repository sudo-project, con “From Michele Piccinni” nei credit, è già un risultato concreto e verificabile. Sul caso Ubuntu. Il finding più significativo dal punto di vista pratico non risiede nella deny-list di env.c in sé, ma nell’interazione tra quel gap e la configurazione sudoers di default di Ubuntu. Un’installazione stock di Ubuntu 22.04 dà ai membri del gruppo sudo il permesso implicito SETENV, rendendo sudo -E + una qualsiasi delle sette variabili un percorso valido di local privilege escalation senza alcuna errata configurazione da parte dell’amministratore. Questo è il tipo di finding che emerge dal seguire la ricerca fino alla sua conclusione logica piuttosto che fermarsi all’analisi del codice sorgente. La disclosure coordinata con Todd Miller ricorda che ricerca responsabile e comunicazione trasparente con il maintainer producono risultati di sicurezza migliori per tutti. Il fix upstream raggiungerà le distribuzioni di tutto il mondo, chiudendo questi gap per milioni di sistemi.
blog.8bitsecurity.comMar 31, 2026extracted
CISA Adds CVE-2025-53521 to KEV After Active F5 BIG-IP APM Exploitation
The U.S. Cybersecurity and Infrastructure Security Agency (CISA) on Friday added a critical security flaw impacting F5 BIG-IP Access Policy Manager (APM) to its Known Exploited Vulnerabilities (KEV) catalog, citing evidence of active exploitation. The vulnerability in question is CVE-2025-53521 (CVSS v4 score: 9.3), which could allow a threat actor to achieve remote code execution. "When a BIG-IP APM access policy is configured on a virtual server, specific malicious traffic can lead to Remote Code Execution (RCE)," according to a description of the flaw in CVE.org. While the shortcoming was initially categorized and remediated as a denial-of-service (DoS) vulnerability with a CVSS v4 score of 8.7, F5 said it has been reclassified as a case of RCE in light of "new information obtained in March 2026." The company has since updated its advisory to confirm that the vulnerability "has been exploited in the vulnerable BIG-IP versions." It did not share any additional details on who may be behind the exploitation activity. However, F5 published a number of indicators that can be used to assess if the system has been compromised - File-related indicators - - Presence of /run/bigtlog.pipe and/or /run/bigstart.ltm. - Mismatch of file hashes when compared to known good versions of /usr/bin/umount and/or /usr/sbin/httpd. - Mismatch of file sizes or timestamps when compared to known good versions of /usr/bin/umount and/or /usr/sbin/httpd. - Each release and EHF may have different file sizes and timestamps. Log-related indicators - - An entry in "/var/log/restjavad-audit. .log" showing a local user accessing the iControl REST API from localhost. - An entry in "/var/log/auditd/audit.log. " showing a local user accessing the iControl REST API from localhost to disable SELinux. - Log messages in "/var/log/audit" show the results of a command being run in the audit log. Other TTPs observed include - - Modifications to the underlying components that the system integrity checker, sys-eicheck, relies on, resulting in a failure of the tool, specifically /usr/bin/umount and/or /usr/sbin/httpd, indicating unexpected changes to the system software as mentioned above. - HTTP/S traffic from the BIG-IP system that contains HTTP 201 response codes and CSS content-type to disguise the attacker's activities. - Changes to the following three files, although their presence alone does not signal a security issue - - /var/sam/www/webtop/renderer/apm_css.php3 - /var/sam/www/webtop/renderer/full_wt.php3 - /var/sam/www/webtop/renderer/webtop_popup_css.php3 "We have observed cases of webshell being written to disk; however, the webshells have been observed to work in memory only, meaning the files listed above might not be modified," F5 cautioned. The issue impacts the following versions - 17.5.0 - 17.5.1 (Fixed in version 17.5.1.3) 17.1.0 - 17.1.2 (Fixed in version 17.1.3) 16.1.0 - 16.1.6 (Fixed in version 16.1.6.1) 15.1.0 - 15.1.10 (Fixed in version 15.1.10.8) In light of active exploitation, Federal Civilian Executive Branch (FCEB) agencies have been given until March 30, 2026, to apply the fixes to secure their networks. "When F5 CVE-2025-53521 first emerged last year as a denial-of-service issue, it didn't immediately signal urgency, and many system administrators likely prioritized it accordingly," watchTowr CEO and founder Benjamin Harris said in a statement shared with The Hacker News. "Fast forward to today's big 'yikes' moment: the situation has changed significantly. What we're observing now is pre-auth remote code execution and evidence of in-the-wild exploitation, with a CISA KEV listing to back it up. That's a very different risk profile than what was initially communicated." Defused Cyber, in an X post, has also confirmed that it's seeing "acute scanning activity" for vulnerable F5 BIG-IP devices following the addition of CVE-2025-53521 to the KEV catalog. "This actor is hitting /mgmt/shared/identified-devices/config/device-info which is a F5 BIG-IP REST API endpoint used to retrieve system-level information, such as hostname, machine ID, and base MAC address," it said.
thehackernews.comMar 28, 2026extracted
Langflow: rilevata 0-day per la CVE-2026-33017
Langflow: rilevata 0-day per la CVE-2026-33017 Alert AL03/260323/CSIRT-ITA Sintesi Rilevato lo sfruttamento attivo delle vulnerabilità CVE-2026-33017 - con gravità “critica” e per la quale risulta disponibile in rete anche un Proof of Concept (PoC) - che interessa il software Langflow, nota piattaforma open-source che permette di costruire, testare e distribuire applicazioni e agenti basati su intelligenza artificiale. Tipologia Remote Code Execution Descrizione È stato recentemente rilevato lo sfruttamento attivo della vulnerabilità identificata tramite la CVE-2026-33017 di tipo “Code Injection” e con score CVSS v3.x pari a 8.8 che interessa la piattaforma Langflow, nota piattaforma open-source che permette di costruire, testare e distribuire applicazioni e agenti basati su intelligenza artificiale. Tale vulnerabilità potrebbe consentire, a un utente malintenzionato remoto, l’esecuzione di codice arbitrario sul sistema interessato tramite richieste POST opportunamente predisposte. La vulnerabilità consente a un attaccante, remoto non autenticato l’esecuzione, l’esecuzione di codice arbitrario sul sistema target, mediante l'invio di richieste HTTP POST opportunamente predisposte verso l'endpoint /api/v1/build_public_tmp. Prodotti e versioni affette Langflow 1.9.x , versioni precedenti alla 1.9.0 Azioni di Mitigazione In attesa del rilascio delle correttive di sicurezza da parte del vendor, si raccomanda di valutare l'implementazione delle seguenti contromisure: Misure di Prevenzione e Mitigazione Restrizione Accesso Rete: Inibire l'esposizione diretta dell'interfaccia web su internet. Implementare un gateway di accesso sicuro (VPN, Zero Trust) o un Reverse Proxy dotato di autenticazione forte (OAuth2, OIDC, SAML) a monte dell'applicazione, adottando un modello deny by default che consenta l’accesso esclusivamente da IP e/o reti fidate. Interdizione Endpoint Vulnerabile: Configurare il Web Application Firewall (WAF) o il Reverse Proxy per bloccare ogni richiesta HTTP (indipendentemente dal metodo utilizzato) verso il path /api/v1/build_public_tmp. Hardening delle Configurazioni: Disabilitare l'accesso automatico, impostando la variabile d'ambiente LANGFLOW_AUTO_LOGIN=false. Nota: si tratta di una misura di hardening complementare per prevenire l'acquisizione immediata di privilegi amministrativi, ma non mitiga la vulnerabilità RCE sottostante. Hardening dei Processi: Vincolare l'esecuzione dell'istanza Langflow a un utente di sistema dedicato (UID/GID non-root). Implementare il confinamento a livello Kernel mediante l'attivazione di profili AppArmor/SELinux e filtri seccomp per limitare le system call autorizzate. Imporre il flag no-new-privileges per inibire tentativi di escalation locale e configurare il filesystem in modalità Read-Only ove possibile. Bonifica e Post-Compromissione Valutazione Esposizione: Qualora l’istanza sia stata esposta direttamente su Internet priva di adeguati controlli di accesso, è da considerarsi come potenzialmente compromessa. Si raccomanda di procedere con attività di bonifica o ripristino da un backup noto come integro. Verifica Integrità dei Flow (Artifact Poisoning): Ispezionare i grafi e i flow salvati (nel database o nei file export) per identificare la presenza di nodi custom o script iniettati. Un attaccante può aver inserito "backdoor logiche" che eseguono codice malevolo ogni volta che un utente legittimo avvia un flow. Rotazione Segreti e Credenziali: Procedere alla revoca e rigenerazione di tutte le API Key (OpenAI, Anthropic, Google Vertex, ecc.), connessioni a database (SQL/Vector) e chiavi di accesso cloud configurate nell'istanza. Includere nella rotazione eventuali token applicativi e chiavi di firma (es. JWT secret). Audit Utenti e Sessioni: Ispezionare il database applicativo per identificare account amministrativi non autorizzati creati durante l'esposizione. Procedere al reset dei token di sessione per forzare la disconnessione di eventuali attori malevoli persistenti. Attività di Monitoraggio (Detection) Analisi Log HTTP: Verificare, nei log di accesso, la presenza di qualsiasi risposta HTTP (non limitandosi al codice 200 OK) associata a richieste verso l'endpoint /api/v1/build_public_tmp provenienti da indirizzi IP non noti. Monitoraggio Outbound: Ispezionare il traffico di rete in uscita per identificare tentativi di connessione verso domini sospetti o IP remoti, non riconducibili ai fornitori di modelli AI (esfiltrazione dati o Reverse Shell). Includere l'analisi di query DNS anomale verso servizi di tunneling. Analisi dei Processi: Monitorare l'esecuzione di processi figli anomali generati dall'applicazione, con particolare attenzione a interpreti di comandi (sh, bash) o utility di rete (curl, wget, nc), analizzando pattern tipici di esecuzione remota (es. python -c, pipeline curl|bash).
acn.gov.itMar 23, 2026extracted
⚡ Weekly Recap: Chrome 0-Days, Router Botnets, AWS Breach, Rogue AI Agents & More
Some weeks in security feel normal. Then you read a few tabs and get that immediate “ah, great, we’re doing this now” feeling. This week has that energy. Fresh messes, old problems getting sharper, and research that stops feeling theoretical real fast. A few bits hit a little too close to real life, too. There’s a good mix here: weird abuse of trusted stuff, quiet infrastructure ugliness, sketchy chatter, and the usual reminder that attackers will use anything that works. Scroll on. You’ll see what I mean. ⚡ Threat of the Week Google Patches 2 Actively Exploited Chrome 0-Days — Google released security updates for its Chrome web browser to address two high-severity vulnerabilities that it said have been exploited in the wild. The vulnerabilities related to an out-of-bounds write vulnerability in the Skia 2D graphics library (CVE-2026-3909) and an inappropriate implementation vulnerability in the V8 JavaScript and WebAssembly engine (CVE-2026-3910) that could result in out-of-bounds memory access or code execution, respectively. Google did not share additional details about the flaws, but acknowledged that there exist exploits for both of them. The issues were addressed in Chrome versions 146.0.7680.75/76 for Windows and Apple macOS, and 146.0.7680.75 for Linux. Detection Starts the Clock. Response Decisions Shape the Outcome When incidents escalate, early decisions determine containment and impact. Join this SANS IR Command Roundtable to learn how experienced teams avoid investigation drift, improve coordination, and execute faster response across cloud, enterprise, and operational environments. Watch the Webcast ➝ 🔔 Top News Meta to Discontinue Instagram E2EE in May 2026 — Meta announced plans to discontinue support for end-to-end encryption (E2EE) for chats on Instagram after May 8, 2026. In a statement shared with The Hacker News, a Meta spokesperson said, "Very few people were opting in to end-to-end encrypted messaging in DMs, so we're removing this option from Instagram in the coming months. Anyone who wants to keep messaging with end-to-end encryption can easily do that on WhatsApp." Authorities Disrupt SocksEscort Service — A court-authorized international law enforcement operation dismantled a criminal proxy service named SocksEscort that enslaved thousands of residential routers worldwide into a botnet for committing large-scale fraud. "The malware allowed SocksEscort to direct internet traffic through the infected routers. SocksEscort sold this access to its customers," the U.S. Justice Department said. The main thing to note here is that SocksEscort was powered by AVrecon, a malware written in C to explicitly target MIPS and ARM architectures via known security flaws in edge network devices. The malware also featured a novel persistence mechanism that involved flashing custom firmware, which intentionally disables future updates, permanently transforming SOHO routers into SocksEscort proxy nodes to blindside corporate monitoring. UNC6426 Exploits nx npm Supply Chain Attack to Gain AWS Admin Access in 72 Hours — A threat actor known as UNC6426 leveraged keys stolen following the supply chain compromise of the nx npm package in August 2025 to completely breach a victim's AWS environment within 72 hours. UNC6426 used the access to abuse the GitHub-to-AWS OpenID Connect (OIDC) trust and create a new administrator role in the cloud environment, Google said. Subsequently, this role was abused to exfiltrate files from the client's Amazon Web Services (AWS) Simple Storage Service (S3) buckets and perform data destruction in their production cloud environments. KadNap Enslaves Network Devices to Fuel Illegal Proxy — A takedown-resistant botnet comprising more than 14,000 routers and other network devices has been conscripted into a proxy network that anonymously ferries traffic used for cybercrime. The botnet, named KadNap, exploits known vulnerabilities in Asus routers (among others), leveraging the initial access to drop shell scripts that reach out to a peer-to-peer network based on Kademlia for decentralized control. Infected devices are being used to fuel a proxy service named Doppelganger that, for a fee, tunnels customers' internet traffic through residential IP addresses, offering a way for attackers to blend in and make it harder to differentiate malicious traffic from legitimate activity. APT28 Strikes with Sophisticated Toolkit — The Russian threat actor known as APT28 has been observed using a bespoke toolkit in recent cyber espionage campaigns targeting Ukrainian cyber assets. The primary components of the toolkit are two implants, one of which employs techniques from a malware framework the threat actor used in 2010s, while the other is a heavily modified version of the COVENANT framework for long-term spying. COVENANT is used in concert with BEARDSHELL to facilitate data exfiltration, lateral movement, and execution of PowerShell commands. Also alongside these tools is a malware named SLIMAGENT that shares overlaps with XAgent. ️🔥 Trending CVEs New vulnerabilities show up every week, and the window between disclosure and exploitation keeps getting shorter. The flaws below are this week's most critical — high-severity, widely used software, or already drawing attention from the security community. Check these first, patch what applies, and don't wait on the ones marked urgent — CVE-2026-3909, CVE-2026-3910, CVE-2026-3913 (Google Chrome), CVE-2026-21666, CVE-2026-21667, CVE-2026-21668, CVE-2026-21672, CVE-2026-21708, CVE-2026-21669, CVE-2026-21671 (Veeam Backup & Replication), CVE-2026-27577, CVE-2026-27493, CVE-2026-27495, CVE-2026-27497 (n8n), CVE-2026-26127, CVE-2026-21262 (Microsoft Windows), CVE-2019-17571, CVE-2026-27685 (SAP), CVE-2026-3102 (ExifTool for macOS), CVE-2026-27944 (Nginx UI), CVE-2025-67826 (K7 Ultimate Security), CVE-2026-26224, CVE-2026-26225 (Intego X9), CVE-2026-29000 (pac4j-jwt), CVE-2026-23813 (HPE Aruba Networking AOS-CX), CVE-2025-12818 (PostgreSQL), CVE-2026-2413 (Ally WordPress plugin), CVE-2026-0953 (Tutor LMS Pro WordPress plugin), CVE-2026-25921 (Gogs), CVE-2026-2833, CVE-2026-2835, CVE-2026-2836 (Cloudflare Pingora), CVE-2026-24308 (Apache ZooKeeper), CVE-2026-3059, CVE-2026-3060, CVE-2026-3989 (SGLang), CVE-2026-0231 (Palo Alto Networks Cortex XDR Broker VM), CVE-2026-20040, CVE-2026-20046 (Cisco IOS XR Software), CVE-2025-65587 (graphql-upload-minimal), CVE-2026-3497 (OpenSSH), CVE-2026-26123 (Microsoft Authenticator for Android and iOS), and CVE-2025-61915 (CUPS). 🎥 Cybersecurity Webinars Stop Guessing: Automate Your Defense Against Real-World Attacks → Learn how to move beyond basic security checklists by using automation to test your defenses against real-world attacks. Experts will show you why traditional testing often fails and how to use continuous, data-driven tools to find and fix gaps in your protection. You will learn how to prove your security actually works without increasing your manual workload. Fix Your Identity Security: Closing the Gaps Before Hackers Find Them → This webinar covers a new study about why many companies are struggling to keep their user accounts and digital identities safe. Experts share findings from the Ponemon Institute on the biggest security gaps, such as disconnected apps and the new risks created by AI. You will learn simple, practical steps to fix these problems and get better control over who has access to your company's data. The Ghost in the Machine: Securing the Secret Identities of Your AI Agents → As artificial intelligence (AI) begins to act on its own, businesses face a new challenge: how to give these "AI agents" the right digital IDs. This webinar explains why current security for humans doesn't work for autonomous bots and how to build a better system to track what they do. You will learn simple, real-world steps to give AI agents secure identities and clear rules, ensuring they don't accidentally expose your private company data. 📰 Around the Cyber World Fake Google Security Check Drops Browser RAT — A web page mimicking a Google Account security page has been spotted delivering a fully featured browser-based surveillance toolkit that takes the form of a Progressive Web App (PWA). "Disguised as a routine security checkup, it walks victims through a four-step flow that grants the attacker push notification access, the device's contact list, real-time GPS location, and clipboard contents—all without installing a traditional app," Malwarebytes said. "For victims who follow every prompt, the site also delivers an Android companion package introducing a native implant that includes a custom keyboard (enabling keystroke capture), accessibility-based screen reading capabilities, and permissions consistent with call log access and microphone recording." Forbidden Hyena Delivers BlackReaperRAT — A hacktivist group known as Forbidden Hyena (aka 4B1D) has distributed RAR archives in December 2025 and January 2026 in attacks targeting Russia that led to the deployment of a previously undocumented remote access trojan called BlackReaperRAT and an updated version of the Blackout Locker ransomware, referred to as Milkyway by the threat actors. BlackReaperRAT is capable of running commands via "cmd.exe," uploading/downloading files, spawning an HTTP shell to receive commands, and spreading the malware to connected removable media. "It carries out destructive attacks against organizations across various sectors located within the Russian Federation," BI.ZONE said. "The group publishes information regarding successful attacks on its Telegram channel. It collaborates with the groups Cobalt Werewolf and Hoody Hyena." Chinese Hackers Target the Persian Gulf region with PlugX — A China-nexus threat actor, likely suspected to be Mustang Panda, has targeted countries in the Persian Gulf region. The activity took place within the first 24 hours of the ongoing conflict in the Middle East late last month. The campaign used a multi-stage attack chain that ultimately deployed a PlugX backdoor variant. "The shellcode and PlugX backdoor used obfuscation techniques such as control flow flattening (CFF) and mixed boolean arithmetic (MBA) to hinder reverse engineering," Zscaler said. "The PlugX variant in this campaign supports HTTPS for command-and-control (C2) communication and DNS-over-HTTPS (DOH) for domain resolution." Phishing Campaign Uses SEO Poisoning to Steal Data — A phishing campaign has employed SEO poisoning to direct search engine results to fake traffic ticket portals that impersonate the Government of Canada and specific provincial agencies. "The campaign lures victims to a fake 'Traffic Ticket Search Portal' under the pretense of paying outstanding traffic violations," Palo Alto Networks Unit 42 said. "Submitted data includes license plates, address, date of birth, phone/email, and credit card numbers." The phishing pages utilize a "waiting room" tactic where the victim's browser polls the server every two seconds and triggers redirects based on specific status codes. Roundcube Exploitation Toolkit Discovered — Hunt.io said it discovered a Roundcube exploitation toolkit on an internet-exposed directory on 203.161.50[.]145. It's worth noting that Russian threat actors like APT28, Winter Vivern, and TAG-70 have repeatedly targeted Roundcube vulnerabilities to breach Ukrainian organizations. "The directory included development and production XSS payloads, a Flask-based command-and-control server, CSS-injection tooling, operator bash history, and a Go-based implant deployed on a compromised Ukrainian web application," the company said, attributing it with medium to high confidence to APT28, citing overlaps with Operation RoundPress. The toolkit, dubbed Roundish, supports credential harvesting, persistent mail forwarding, bulk email exfiltration, address book theft, and two-factor authentication (2FA) secret extraction, mirroring a feature present in MDAEMON. One of the primary targets of the attack is mail.dmsu.gov[.]ua, a Roundcube webmail instance associated with Ukraine's State Migration Service (DMSU). Besides the possibility of a shared development lineage, Roundish introduces four new components not previously documented in APT28 webmail activity, including a CSS-based side-channel module, browser credential stealer, and a Go-based backdoor that provides persistence via cron, systemd, and SELinux. The CSS injection component is designed to progressively extract characters from Roundcube's document object model (DOM) without injecting any JavaScript into the victim's page. The technique is likely used for targeting Cross-Site Request Forgery (CSRF) tokens or email UIDs. Central to the Roundish toolkit is an XSS payload that's engineered to steal the victim's email address, harvest account credentials, redirect all incoming emails to a Proton Mail address, export mailbox data from the victim's Inbox and Sent folders, and gather the victim's complete address book. "The combination of hidden autofill credential harvesting, server-side mail forwarding persistence, bulk mailbox exfiltration, and browser credential theft reflects a modular approach designed for sustained access," Hunt.io said. "From a defensive perspective, password resets alone are not sufficient in cases like this. Mail forwarding rules, Sieve filters, and multi-factor authentication secrets must be audited and reset." Phishing Campaign Targeting AWS Console Credentials — An active adversary-in-the-middle (AiTM) phishing campaign is using fake security alert emails to steal AWS Console credentials, per Datadog. "The phishing kit proxies authentication to the legitimate AWS sign-in endpoint in real time, validating credentials before redirecting victims and likely capturing one-time password (OTP) codes," the company said. "This campaign does not exploit AWS vulnerabilities or abuse AWS infrastructure." Post-compromise console access has been observed within 20 minutes of credential submission. These efforts originated from Mullvad VPN infrastructure. Malicious npm Packages Deliver Cipher stealer — Two new malicious npm packages, bluelite-bot-manager and test-logsmodule-v-zisko, were found to deliver via Dropbox a Windows executable designed to siphon sensitive data, including Discord totems, credentials from Chrome, Edge, Opera, Brave, and Yandex browsers, and seed files from cryptocurrency wallet apps like Exodus. from compromised hosts using a stealer named Cipher stealer. "The stealer also uses an embedded Python script and a secondary payload downloaded from GitHub," JFrog said. GIBCRYPTO Ransomware Detailed — A new ransomware called GIBCRYPTO comes with the ability to capture keystrokes and corrupt the Master Boot Record (MBR) so that any attempt to restart the system will cause the system to run into an error. The ransomware uses the Salsa20 algorithm for encryption. It's suspected to be part of Snake Keylogger, indicating the malware authors' attempts to diversify beyond information theft. The development comes as Sygnia highlighted SafePay's OneDrive-based data exfiltration technique during a ransomware attack after breaching a victim by leveraging a FortiGate firewall flaw and a misconfigured administrative account. "SafePay gained initial access by exploiting a firewall misconfiguration, which enabled them to obtain local administrative credentials," the company said. "They rapidly escalated discovery and enumeration activities to identify high-value targets for lateral movement, demonstrating a structured and methodical approach to mapping the environment. Within a matter of hours, SafePay escalated to domain administrator access." The attack culminated in the deployment of ransomware, encrypting more than 60 servers. Fraudulent Account Registration Activity Originating from Vietnam — A sprawling cybercrime ecosystem based in Vietnam has been linked to a cluster of fraudulent account registration activity on platforms like LinkedIn, Instagram, Facebook, and TikTok. In these attacks, attributed to O-UNC-036, the threat actors rely on disposable email addresses in order to execute SMS pumping attacks, also called International Revenue Sharing Fraud (IRSF). "In this scheme, malicious actors automate the creation of puppet accounts in a targeted service provider," Okta said. "Fraudsters use these account registrations to trigger SMS messages to premium rate phone numbers and profit from charges incurred. This activity can prove costly for service providers who use SMS to verify registration information in customer accounts or to send multi-factor authentication (MFA) security codes." O-UNC-036 has also been linked to a cybercrime-as–a-service (CaaS) ecosystem that provides paid infrastructure and services to facilitate online fraud. The web-based storefronts are hosted in Vietnam and specialize in the sales of web-based accounts. Hijacked AppsFlyer SDK Distributes Crypto Clipper — The AppsFlyer Web SDK was briefly hijacked to serve malicious code to steal cryptocurrency in a supply chain attack. The clipper malware payload came with capabilities to intercept cryptocurrency wallet addresses entered on websites and replace them with attacker-controlled addresses to divert funds to the threat actor. "The AppsFlyer Web SDK was observed serving obfuscated malicious JavaScript instead of the legitimate SDK from websdk.appsflyer[.]com," Profero said. "The malicious payload appears to have been designed for stealth and compatibility, preserving legitimate SDK functionality while adding hidden browser hooks and wallet-hijacking logic." The incident has since been resolved by AppsFlyer. Operation CamelClone Targets Government and Defense Entities — A new cyber espionage campaign dubbed Operation CamelClone has targeted governments and defense entities in Algeria, Mongolia, Ukraine, and Kuwait using malicious ZIP archives that contain a Windows shortcut (LNK) file, which, when executed, delivers a JavaScript loader named HOPPINGANT. The loader then delivers additional payloads for establishing C2 and exfiltrating data to the MEGA cloud storage service. "One interesting aspect of this campaign is that the threat actor does not rely on traditional command-and-control infrastructure," Seqrite Labs said. "Instead, the payloads are hosted on a public file-sharing service, filebulldogs[.]com, while stolen data is uploaded to MEGA storage using the legitimate tool Rclone." The activity has not been attributed to any known threat group. How Threat Actors Exfiltrate Credentials Using Telegram Bots — Threat actors are abusing the Telegram Bot API to exfiltrate data via text messages or arbitrary file uploads, highlighting how legitimate services can be weaponized to evade detection. Agent Tesla Keylogger is by far the most prominent example of a malware family that uses Telegram for C2. "In general, Telegram C2s appear to be most popular among information stealers, possibly due to Telegram's technically legitimate nature and because information stealers typically only need to exfiltrate data passively rather than provide complex communications beyond simple message or file transfers," Cofense said. Microsoft Launches Copilot Health — Microsoft has become the latest company after OpenAI and Anthropic to launch a dedicated "secure space" called Copilot Health that integrates medical records, biometric data from wearables, and lab test results to give personalized advice in the U.S. "Copilot Health brings together your health records, wearable data, and health history into one place, then applies intelligence to turn them into a coherent story," the company said. Like OpenAI and Anthropic, Microsoft emphasized that Copilot Health isn't meant to replace professional medical care. Rogue AI Agents Can Work Together to Engage in Offensive Behaviors — According to a new report from artificial intelligence (AI) security company Irregular, agents can work together to hack into systems, escalate privileges, disable endpoint protection, and steal sensitive data while evading pattern-matching defenses. What's notable is that the experiment did not rely on adversarial prompting or deliberately unsafe system design. "In one case, an agent convinced another agent to carry out an offensive action, a form of inter-agent collusion that emerged with no external manipulation," Irregular said. "This scenario demonstrates two compounding risks: inter-agent persuasion can erode safety boundaries, and agents can independently develop techniques to circumvent security controls. When an agent is given access to tools or data, particularly but not exclusively shell or code access, the threat model should assume that the agent will use them, and that it will do so in unexpected and possibly malicious ways." 🔧 Cybersecurity Tools Dev Machine Guard → It is a free, open-source tool that scans your computer to show you exactly what developer tools and scripts are running. It creates a simple list of your AI coding assistants, code editor extensions, and software packages to help you find anything suspicious or outdated. It is a single script that works in seconds to give you better visibility into the security of your local coding environment. Trajan → It is an automated security tool designed to find hidden vulnerabilities in "service meshes," which are the systems that manage how different parts of a large software application talk to each other. Because these systems are complex, it is easy for engineers to make small mistakes in the settings that allow hackers to bypass security or steal data. Trajan works by scanning these configurations to spot those specific errors and helping developers fix them before they can be exploited. Disclaimer: For research and educational use only. Not security-audited. Review all code before use, test in isolated environments, and ensure compliance with applicable laws. Conclusion There’s a lot packed in here, and not in a neat way. Some of it is the usual recycled chaos, some of it feels a little more deliberate, and some of it has that nasty “this is going to show up everywhere by next week” energy. Anyway — enough throat-clearing. Here’s the stuff worth your attention.
thehackernews.comMar 16, 2026extracted
Edge computing’s biggest lie: “We’ll patch it later”
Edge computing’s biggest lie: “We’ll patch it later” Edge computing is spreading fast, from factory floors to remote infrastructure. But many of these systems are hard to maintain once they are deployed. Devices may run old kernels, custom board support packages, or stacks that no one can rebuild years later. Updates can fail due to weak connectivity or power loss, and a mistake can brick thousands of systems at once. Add AI workloads that cannot tolerate downtime, and patching becomes even harder. In this Help Net Security interview, Piotr Buliński, CTO of Qbee, digs into the edge equivalent of “snowflake servers,” why cloud habits break in the field, and what it takes to monitor and update fleets safely. What is the edge equivalent of “snowflake servers” in the data center, and how does that problem scale into a fleet-wide risk? In data centers, a ‘snowflake’ is a server whose unique configuration makes it impossible to reproduce. In the Edge and Embedded world, the equivalent of this is called a ‘Frozen Device.’ Such devices are run on a poorly maintained software stack – often a custom kernel or a proprietary Board Support Package (BSP) – that has become a black box over time. The longer these devices are neglected, the worse the security risk. As a general rule, if you haven’t checked in on a device several years after deployment, you aren’t just managing hardware; you’re managing a liability. Unlike in data centers, where on-site technical support (known as remote hands) can swap a drive or a serial console can rescue a bricked server, an edge device is often physically or geographically isolated and managed by non-technical personnel. Pair this technical atrophy with a large number of unmaintained devices and risk can scale into a fleet-wide crisis. If the original build environment is gone, the toolchains are deprecated, or the security patches for that specific legacy kernel no longer exist, an entire fleet is a sitting duck for bad actors. Under upcoming regulations like the EU’s Cyber Resilience Act (CRA), the inability to patch isn’t just a technical failure. It’s soon to become a compliance violation that carries significant financial and reputational penalties. Companies can no longer optimize for ‘Day 1’ deployment while ignoring ‘Day 2’ lifecycle management. This shortsited approach to IoT is essentially betting that the threat landscape won’t evolve. And let me tell you…it always does. What is the most common false assumption teams make when they apply cloud operating models to edge environments? The most dangerous assumption teams make is that they can apply a “Cloud MVP” (minimum viable product), using a product that’s just good enough – with the intention of figuring out the operational details after launch. In the cloud, a failed deployment is an issue with a five-minute fix. In edge computing though, it can be a catastrophic, fleet-wide “bricking” event that makes a server, computer, or IoT device completely inoperable. If you don’t architect for a production-grade foundation, specifically a robust OS and atomic (all-or-nothing) OTA update mechanism from Day 1, you are building on an insecure foundation. Unlike servers that are always reachable, edge devices may be powered off for months. If your update infrastructure can’t handle long-term dormancy or interrupted power, you’ll be stuck maintaining an inferior legacy code for years just to keep the lights on. Another aspect to this is environmental volatility. While cloud models assume “infinite” resources such as stable power and reliable high-speed networking, at the edge, an update often fails due to a simple power outage or a flaky cellular link. Without a mechanism that can automatically revert to a known-working state, a failed update requires a physical site visit. The cost of sending an engineer into the field can instantly destroy the margins of a project. Perhaps the most overlooked area is observability and post-launch blindness. In a data center, teams can instrument monitoring post-launch because they always have eyes on the server. At the edge, if you don’t build monitoring into the initial image, you lose all visibility. If a bug prevents an update from rolling out and you don’t have the telemetry to see why, teams then lose the ability to mitigate the risk. Losing the ability to manage your assets can be just as serious as losing your data. Are you seeing cases where AI workloads at the edge force organizations to rethink patch windows entirely because they cannot afford downtime? Absolutely. AI at the edge has fundamentally killed the traditional patch window. In a data center, a 10-minute reboot is an inconvenience; at the edge, if that AI is performing predictive maintenance on a high-speed production line or monitoring a power grid, 10 minutes of downtime creates a huge gap where teams are completely blind to potentially major failures. As a result, we are seeing organizations rethink their entire stack to achieve zero-downtime updates. This is driving two major shifts. The first being decoupling the model from the OS. Instead of one monolithic firmware update, teams are moving toward containerized architectures. This allows them to ‘hot-swap’ AI models or security patches for the inference engine without rebooting the entire system or stopping the primary application. The second is A/B redundancy as a standard. To avoid the risk of a botched update ‘bricking’ a critical AI node, we’re seeing the ‘Blue-Green’ deployment model move from the cloud to the edge. The device maintains two identical environments; the new model/patch is loaded onto the ‘passive’ side, verified, and then the system flips over in milliseconds. If your edge AI solution requires you to stop the business to secure the device, you haven’t built a modern edge solution, you’ve created a bottleneck. The goal now is ‘in-flight patching’, the ability to evolve the system’s intelligence without ever losing sight of the physical assets it protects. Many organizations want cloud-style CI/CD velocity at the edge. What part of the pipeline tends to break first when teams try to implement that? In the cloud, Continuous Integration and Continuous Delivery (CI/CD) is a manageable software-to-software transaction in which environments are very predictable. At the edge however, CI/CD hits a wall because of the validation gap – where real-world device conditions can’t be reliably tested before deployment. While building and shipping are largely solved problems, verifying that a build “works” before it hits the field is exponentially more complex. The pipeline typically breaks in two specific places: The first of which is the flaky Hardware-in-the-Loop (HiL) trap. In order for teams to gain true confidence in their IoT deployments, they eventually have to move beyond software simulation and use actual hardware rigs for testing. This requires a significant infrastructure investment – often using tools like Labgrid (for automated hardware control) or custom test harnesses. The “break” happens when the test infrastructure itself becomes unreliable. If a cable is loose or a relay fails, teams get flaky tests. In a CI/CD world, flaky tests destroy developer trust and halt the pipeline. Then we have the Security “Parity” Paradox. Teams often take shortcuts by disabling security features (like Secure Boot, disk encryption, or strict SELinux policies) in the test environment to make automation easier. This creates a dangerous ‘Parity Gap.’ It may sound obvious, but if you aren’t testing with the security features enabled, you aren’t testing the real thing. It is very common to see a build pass CI perfectly, only to fail in production because a new security policy blocked a critical process. Ultimately, if your test environment doesn’t mirror the physical and security constraints of the field, your CI/CD pipeline is just a machine for shipping bugs faster. If you want predictable edge deployments, you have to treat your test hardware with the same rigor as your production hardware. How do you build trust in fleet-wide monitoring when devices can be offline, partially compromised, or reporting inconsistent data? Trust at the edge isn’t built on 100% uptime; it’s built on verifiable identity and contextual intelligence. First, you must establish a cryptographically verifiable identity. Rather than just a serial number, you need a hardware-backed root of trust, using a Trusted Platform Module (TPM) or Trusted Execution Environment (TEE), to handle mutual Transport Layer Security (mTLS) certificates. This ensures that the data you’re seeing came from the device you think it did, preventing spoofed telemetry from compromised nodes. We also have to treat inconsistency as a diagnostic signal. A trusted device can still report bad data due to sensor failure or local tampering and a mature monitoring system should automatically flag outliers by comparing a device’s behavior against its peer group or historical baseline. If one device in a fleet of 1,000 starts reporting impossible temperatures or strange access logs, that will be your starting point for a targeted investigation. Finally, the definition of ‘offline’ is in need of an update. In an edge environment, connectivity is often intermittent by design. Trust comes from being able to differentiate between expected silence during sleep or known dead zones and anomalous silence (a device that stopped checking in right after a failed login attempt). By providing granular information like this, we ensure that an engineer is only dispatched when absolutely necessary. Moreover, when the engineer arrives on-site, they already have the diagnostic data they need to fix the problem on the first visit.
helpnetsecurity.comFeb 13, 2026extracted
New LandFall spyware exploited Samsung zero-day via WhatsApp messages
A threat actor exploited a zero-day vulnerability in Samsung’s Android image processing library to deploy a previously unknown spyware called 'LandFall' using malicious images sent over WhatsApp. The security issue was patched this year in April, but researchers found evidence that the LandFall operation was active since at least July 2024, and targeted select Samsung Galaxy users in the Middle East. Identified as CVE-2025-21042, the zero-day is an out-of-bounds write in libimagecodec.quram.so and has a critical severity rating. A remote attacker successfully exploiting it can execute arbitrary code on a target device. According to researchers at Palo Alto Networks’ Unit 42, the LandFall spyware is likely a commercial surveillance framework used in targeted intrusions. The attacks begin with the delivery of a malformed .DNG raw image format with a .ZIP archive appended towards the end of the file. Unit 42 researchers retrieved and examined samples that were submitted to the VirusTotal scanning platform starting July 23, 2024, indicating WhatsApp as the delivery channel, based on the filenames used. From a technical perspective, the DNGs embed two main components: a loader (b.so) that can retrieve and load additional modules, and a SELinux policy manipulator (l.so), which modifies security settings on the device to elevate permissions and establish persistence. According to the researchers, LandFall can fingerprint devices based on hardware and SIM IDs (IMEI, IMSI, the SIM card number, user account, Bluetooth, location services, or the list of installed applications. However, additional capabilities observed include executing modules, achieving persistence, evading detection, and bypassing protections. Among the spying features, the malware counts: microphone recording call recording location tracking accessing photos, contacts, SMS, call logs, and files accessing the browsing history According to Unit 42’s analysis, the spyware targets Galaxy S22, S23, and S24 series devices, as well as Z Fold 4 and Z Flip 4, covering a broad range of Samsung’s latest flagship models, excluding the latest S25 series devices. It’s worth noting that LandFall and its use of DNG images is another case of broader exploitation seen recently in commercial spyware tools. There have been exploitation chains in the past involving the DNG format for Apple iOS, with CVE-2025-43300, and also for WhatsApp, with CVE-2025-55177. Samsung also fixed CVE-2025-21043 recently, which also impacts libimagecodec.quram.so, after WhatsApp security researchers discovered and reported it. Attribution murky The data from the VirusTotal samples that the researchers examined indicate potential targets in Iraq, Iran, Turkey, and Morocco. Unit 42 was able to identify and correlate six command-and-control (C2) servers with the LandFall campaign, some of them flagged for malicious activity by Turkey’s CERT. C2 domain registration and infrastructure patterns share similarities with those seen in Stealth Falcon operations, originating from the United Arab Emirates. Another clue is the use of the “Bridge Head” name for the loader component, a naming convention that is commonly seen in NSO Group, Variston, Cytrox, and Quadream products. However, LandFall could not be confidently linked to any known threat groups or spyware vendors. To protect against spyware attacks, apply security updates for your mobile OS and apps promptly, disable automatic media downloading on messaging apps, and consider activating ‘Advanced Protection’ on Android and ‘Lockdown Mode’ on iOS. Overall prevention scores can hide what happens after initial access. Once attackers are using valid credentials, prevention drops sharply. The Blue Report 2026 measures defenses technique by technique across 338 million simulations run in customer production environments. Get the report
bleepingcomputer.comNov 7, 2025extracted
Samsung Zero-Click Flaw Exploited to Deploy LANDFALL Android Spyware via WhatsApp
A now-patched security flaw in Samsung Galaxy Android devices was exploited as a zero-day to deliver a "commercial-grade" Android spyware dubbed LANDFALL in targeted attacks in the Middle East. The activity involved the exploitation of CVE-2025-21042 (CVSS score: 8.8), an out-of-bounds write flaw in the "libimagecodec.quram.so" component that could allow remote attackers to execute arbitrary code, according to Palo Alto Networks Unit 42. The issue was addressed by Samsung in April 2025. "This vulnerability was actively exploited in the wild before Samsung patched it in April 2025, following reports of in-the-wild attacks," Unit 42 said. Potential targets of the activity, tracked as CL-UNK-1054, are located in Iraq, Iran, Turkey, and Morocco based on VirusTotal submission data. The development comes as Samsung disclosed in September 2025 that another flaw in the same library (CVE-2025-21043, CVSS score: 8.8) had also been exploited in the wild as a zero-day. There is no evidence of this security flaw being weaponized in the LANDFALL campaign. Samsung did not immediately respond to a request for comment. It's assessed that the attacks involved sending via WhatsApp malicious images in the form of DNG (Digital Negative) files, with evidence of LANDFALL samples going all the way back to July 23, 2024. This is based on DNG artifacts bearing names like "WhatsApp Image 2025-02-10 at 4.54.17 PM.jpeg" and "IMG-20240723-WA0000.jpg." Itay Cohen, senior principal researcher at Palo Alto Networks Unit 42, told The Hacker News that they have not observed any significant functional changes between the samples from July 2024 and February 2025, when the most recent LANDFALL artifact was uploaded to VirusTotal. LANDFALL, once installed and executed, acts as a comprehensive spy tool, capable of harvesting sensitive data, including microphone recording, location, photos, contacts, SMS, files, and call logs. While Unit 42 said the exploit chain may have involved the use of a zero-click approach to trigger the exploitation of CVE-2025-21042 without requiring any user interaction, there are currently no indications that it has happened or there exists an unknown security issue in WhatsApp to support this hypothesis. The Android spyware is specifically designed to target Samsung's Galaxy S22, S23, and S24 series devices, as well as Z Fold 4 and Z Flip 4, covering some of the flagship devices from the South Korean electronics chaebol, with the exception of the latest generation. It's worth noting that around the same time WhatsApp disclosed that a flaw in its messaging app for iOS and macOS (CVE-2025-55177, CVSS score: 5.4) was chained along with CVE-2025-43300 (CVSS score: 8.8), a flaw in Apple iOS, iPadOS, and macOS, to potentially target less than 200 users as part of a sophisticated campaign. Apple and WhatsApp have since patched the flaws. Unit 42's analysis of the discovered DNG files show that they come with an embedded ZIP file appended to the end of the file, with the exploit being used to extract a shared object library from the archive to run the spyware. Also present in the archive is another shared object that's designed to manipulate the device's SELinux policy to grant LANDFALL elevated permissions and facilitate persistence. The shared object that loads LANDFALL also communicates with a command-and-control (C2) server over HTTPS to enter into a beaconing loop and receive unspecified next-stage payloads for subsequent execution. "At this point, we can't share details about the next-stage payloads delivered from the C2 server," Cohen said. "What we can say is that LANDFALL is a modular spyware framework -- the loader we analyzed is clearly designed to fetch and execute additional components from the C2 infrastructure. Those later stages likely extend its surveillance and persistence capabilities, but they weren’t recovered in the samples available to us." It's currently not known who is behind the spyware or the campaign. That said, Unit 42 said LANDFALL's C2 infrastructure and domain registration patterns dovetail with that of Stealth Falcon (aka FruityArmor), although, as of October 2025, no direct overlaps between the two clusters have been detected. The findings suggest that the delivering LANDFALL is likely part of a broader DNG exploitation wave that also hit iPhone devices via the aforementioned exploit chains. They also highlight how sophisticated exploits can remain accessible in public repositories for extended periods of time, flying under the radar until they can be fully analyzed. "We don't believe this specific exploit is still being used, since Samsung patched it in April 2025," Cohen said. "However, related exploit chains affecting Samsung and iOS devices were observed as recently as August and September, indicating that similar campaigns remained active until very recently. Some infrastructure that might be related to LANDFALL also remains online, which could suggest ongoing or follow-on activity by the same operators." Update The U.S. Cybersecurity and Infrastructure Security Agency (CISA), on November 10, 2025, added CVE-2025-21042 to its Known Exploited Vulnerabilities (KEV) catalog, requiring Federal Civilian Executive Branch (FCEB) agencies to remediate the flaw by December 1, 2025. "Samsung mobile devices contain an out-of-bounds write vulnerability in libimagecodec.quram.so," the agency said. "This vulnerability could allow remote attackers to execute arbitrary code." (The story was updated after publication to clarify details surrounding the use of WhatsApp as a distribution vector for the malware and additional insights from Unit 42.)
thehackernews.comNov 7, 2025extracted
ThreatsDay Bulletin: AI Tools in Malware, Botnets, GDI Flaws, Election Attacks & More
Cybercrime has stopped being a problem of just the internet — it’s becoming a problem of the real world. Online scams now fund organized crime, hackers rent violence like a service, and even trusted apps or social platforms are turning into attack vectors. The result is a global system where every digital weakness can be turned into physical harm, economic loss, or political leverage. Understanding these links is no longer optional — it’s survival. For a full look at the most important security news stories of the week, keep reading. Hidden flaws resurface in Windows coreDetails have emerged about three now-patched security vulnerabilities in Windows Graphics Device Interface (GDI) that could enable remote code execution and information disclosure. These issues – CVE-2025-30388, CVE-2025-53766, and CVE-2025-47984 – involve out-of-bounds memory access triggered through malformed enhanced metafile (EMF) and EMF+ records that can cause memory corruption during image rendering. They are rooted in gdiplus.dll and gdi32full.dll, which process vector graphics, text, and print operations. They were addressed by Microsoft in the Patch Tuesday updates in May, July, and August 2025 in gdiplus.dll versions 10.0.26100.3037 through 10.0.26100.4946 and gdi32full.dll version 10.0.26100.4652. "Security vulnerabilities can persist undetected for years, often resurfacing due to incomplete fixes," Check Point said. "A particular information disclosure vulnerability, despite being formally addressed with a security patch, remained active for years due to the original issue receiving only a partial fix. This example underscores a basic conundrum for researchers: introducing a vulnerability is often easy, fixing it can be difficult, and verifying that a fix is both thorough and effective is even more challenging." Syndicate staffed by fake workers net millionsThree Chinese nationals, Yan Peijian, 39, Huang Qinzheng, 37, and Liu Yuqi, 33, were convicted and sentenced to a little over two years in prison in Singapore for their involvement in hacking into overseas gambling websites and companies for the purposes of cheating during gameplay and stealing databases of personally identifiable information for trade. The three individuals, part of a group of five Chinese nationals and one Singaporean man, were originally arrested and charged in September 2024. "The three accused persons were tasked by the syndicate's group leader to probe sites of interest for system vulnerabilities, conduct penetration attacks, and exfiltrate personal information from the compromised systems," the Singapore Police Force said. "Further investigations revealed that the syndicate possessed foreign government data, including confidential communications." The three defendants were also found to be in possession of tools like PlugX and "hundreds of different remote access trojans" to conduct cyber attacks. According to Channel News Asia, the three men entered the country on fake work permits in 2022 and worked for a 38-year-old Ni-Vanuatu citizen named Xu Liangbiao. They were paid about $3 million for their work. Xu, the alleged leader, is said to have left Singapore in August 2023. His present whereabouts are unknown. AI speeds triage but human skill still neededCheck Point has demonstrated a way by which ChatGPT can be used for malware analysis and flip the balance when it comes to taking apart sophisticated trojans like XLoader, which is designed such that its code decrypts only at runtime and is protected by multiple layers of encryption. Specifically, the research found that cloud-based static analysis with ChatGPT can be combined with Model Context Protocol (MCP) for runtime key extraction and live debugging validation. "The use of AI doesn't eliminate the need for human expertise," security researcher Alexey Bukhteyev said. "XLoader's most sophisticated protections, such as scattered key derivation logic and multi-layer function encryption, still require manual analysis and targeted adjustments. But the heavy lifting of triage, deobfuscation, and scripting can now be accelerated dramatically. What once took days can now be compressed into hours." RondoDox goes from DVRs to enterprise-wide weaponThe malware known as RondoDox has witnessed a 650% increase in exploitation vectors, expanding from niche DVR targeting to enterprise. This includes more than 15 new exploitation vectors targeting LB-LINK, Oracle WebLogic Server, PHPUnit, D-Link, NETGEAR, Linksys, Tenda, TP-Link devices, as well as a new command-and-control (C2) infrastructure on compromised residential IP. Once dropped, the malware proceeds to eliminate competition by killing existing malware such as XMRig and other botnets, disabling SELinux and AppArmor, and running the main payload that's compatible with the system architecture. DHS pushes sweeping biometric rule for immigrationThe U.S. Department of Homeland Security (DHS) has proposed an amendment to existing regulations governing the use and collection of biometric information. The agency has put forth requirements for a "robust system for biometrics collection, storage, and use related to adjudicating immigration benefits and other requests and performing other functions necessary for administering and enforcing immigration and naturalization laws." As part of the plan, any individual filing or associated with a benefit request or other request or collection of information, including U.S. citizens, U.S. nationals, and lawful permanent residents, must submit biometrics, regardless of their age, unless DHS otherwise exempts the requirement. The agency said using biometrics for identity verification and management will assist DHS's efforts to combat trafficking, confirm the results of biographical criminal history checks, and deter fraud. The DHS is taking comments on the proposal until January 2, 2026. Researchers uncover large-scale AWS abuse networkCybersecurity researchers have discovered a new large-scale attack infrastructure dubbed TruffleNet that's built around the open-source tool TruffleHog, which is used to systematically test compromised credentials and perform reconnaissance across Amazon Web Services' (AWS) environments. "In one incident involving multiple compromised credentials, we recorded activity from more than 800 unique hosts across 57 distinct Class C networks," Fortinet said. "This infrastructure was characterized by the use of TruffleHog, a popular open-source secret-scanning tool, and by consistent configurations, including open ports and the presence of Portainer," an open-source management UI for Docker and Kubernetes that simplifies container deployment and orchestration. In these activities, the threat actors make calls to the GetCallerIdentity and GetSendQuota APIs to test whether the credentials are valid and abuse the Simple Email Service (SES). While no follow-on actions were observed by Fortinet, it's assessed that the attacks originate from a possibly tiered infrastructure, with some nodes dedicated to reconnaissance and others reserved for later stages of the attack. Also observed alongside the TruffleNet reconnaissance activity is the abuse of SES for Business Email Compromise (BEC) attacks. It's currently not known if these are directly connected to each other. The development comes as Fortinet revealed that financially motivated adversaries are targeting a broad range of sectors but relying on the same low-complexity, high-return methods, typically gaining initial access through compromised credentials, external remote services like VPNs, and exploitation of public-facing applications. These attacks are often characterized by the use of legitimate remote access tools for secondary persistence and leveraging them for data exfiltration to their infrastructure. FIN7 deploys stealthy SSH backdoor for persistencePRODAFT has revealed that the financially motivated threat actor known as FIN7 (aka Savage Ladybug) has deployed since 2022 a "Windows specific SSH-based backdoor by packaging a self-contained OpenSSH toolset and an installer named install.bat." The backdoor provides attackers with persistent remote access and reliable file exfiltration using an outbound reverse SSH tunnel and SFTP. Cloudflare fends off massive DDoS surge on election dayWeb infrastructure company Cloudflare said Moldova's Central Election Commission (CEC) experienced significant cyber attacks in the days leading to the country's Parliament election on September 28. The CEC also witnessed a "series of concentrated, high-volume (DDoS) attacks strategically timed throughout the day" on the day of the elections. Attacks also targeted other election-related, civil society, and news websites. "These attack patterns mirrored those against the election authority, suggesting a coordinated effort to disrupt both official election processes and the public information channels voters rely on," it said, adding it mitigated over 898 million malicious requests directed at the CEC over a 12-hour period between 09:06:00 UTC and 21:34:00 UTC. Silent Lynx exploits diplomacy themes to breach targetsThe threat actor tracked as Silent Lynx (aka Cavalry Werewolf, Comrade Saiga, ShadowSilk, SturgeonPhisher, and Tomiris) has been observed targeting government entities, diplomatic missions, mining firms, and transportation companies. In one campaign, the adversary singled out organizations involved in Azerbaijan-Russian diplomacy, using phishing lures related to the CIS summit held in Dushanbe around mid-October 2025 to deliver the open-source Ligolo-ng reverse shell and a loader called Silent Loader that's responsible for running a PowerShell script to connect to a remote server. Also deployed is a C++ implant named Laplas that's designed to connect to an external server and receive additional commands for execution via "cmd.exe." Another payload of note is SilentSweeper, a .NET backdoor that extracts and runs a PowerShell Script that acts as a reverse shell. The second campaign, on the other hand, aimed at China-Central Asia relations to distribute a RAR archive that led to the deployment of SilentSweeper. The activity has been codenamed Operation Peek-a-Baku by Seqrite Labs. Doctor Web, in an independent analysis, said it investigated a phishing attack mounted by the threat actor targeting a government-owned organization within the Russian Federation to deliver reverse shell backdoors with the goal of collecting confidential information as well as network configuration data. Cyber gangs blend digital and physical extortion across EuropeEuropean organizations witnessed a 13% increase in ransomware over the past year, with entities in the U.K., Germany, Italy, France, and Spain most affected. A review of data leak sites over the period September 2024–August 2025 has revealed that the number of European victims has increased annually to 1,380. The most targeted sectors were manufacturing, professional services, technology, industrials, engineering, and retail. Since January 2024, over 2,100 victims across Europe have been named on extortion leak sites, with 92% involving file encryption and data theft. Akira (167), LockBit (162), RansomHub (141), INC, Lynx, and Sinobi were the most successful ransomware groups over the period. CrowdStrike said it's also seeing a surge in violence-as-a-service offerings across the continent with the goal of securing big payouts, including physical cryptocurrency theft. Cybercriminals connected to The Com, a loose-knit collective of young, English-speaking hackers, and a Russia-affiliated group called Renaissance Spider have coordinated physical attacks, kidnapping, and arson through Telegram-based networks. Renaissance Spider, which has been active since October 2017, is also said to have emailed fake bomb threats to European entities, likely aiming to undermine support for Ukraine. There have been 17 of these kinds of attacks since January 2024, out of which 13 took place in France. Fake ChatGPT and WhatsApp apps exploit user trustCybersecurity researchers have discovered apps that use the branding of established services like OpenAI's ChatGPT and DALL-E, and WhatsApp. While the fake DALL-E Android app ("com.openai.dalle3umagic") is used for ad traffic generation, the ChatGPT wrapper app connects to legitimate OpenAI APIs while identifying itself as an "unofficial interface" for the artificial intelligence chatbot. Although not outright malicious, impersonation without transparency can expose users to unintended security risks. The counterfeit WhatsApp app, named WhatsApp Plus, masquerades as an upgraded version of the messaging platform, but contains stealthy payloads that can harvest contacts, SMS messages, and call logs. "The flood of cloned applications reflects a deeper problem: brand trust has become a vector for exploitation," Appknox said. "As AI and messaging tools dominate the digital landscape, bad actors are learning that mimicking credibility is often more profitable than building new malware from scratch." Phishers weaponize trusted email accounts post-breachThreat actors are continuing to launch phishing campaigns after their initial compromise by leveraging compromised internal email accounts to expand their reach both within the compromised organization as well as externally to partner entities. "The follow-on phishing campaigns were primarily oriented towards credential harvesting," Cisco Talos said. "Looking forward, as defenses against phishing attacks improve, adversaries are seeking ways to enhance these emails’ legitimacy, likely leading to the increased use of compromised accounts post-exploitation." Asia-wide phishing surge uses multilingual luresRecent phishing campaigns across East and Southeast Asia have been found to leverage multilingual ZIP file lures and shared web templates to target government and financial organizations. "These operations are characterized by multilingual web templates, region-specific incentives, and adaptive payload delivery mechanisms, demonstrating a clear shift toward scalable and automation-driven infrastructure," Hunt.io said. "From China and Taiwan to Japan and Southeast Asia, the adversaries have continuously repurposed templates, filenames, and hosting patterns to sustain their operations while evading conventional detection. The strong overlap in domain structures, webpage titles, and scripting logic indicates a shared toolkit or centralized builder designed to automate payload delivery at scale. This investigation links multiple clusters to a unified phishing toolkit used across Asia." Remote kill-switch fears spark probe into Chinese busesAuthorities in Denmark have launched an investigation following a discovery that electric buses manufactured by the Chinese company Yutong had remote access to the vehicles' control systems and allowed them to be remotely deactivated. This has raised security concerns that the loophole could be exploited to affect buses while in transit. "The testing revealed risks that we are now taking measures against," Bernt Reitan Jenssen, chief executive of the Norwegian public transport authority Ruter, was quoted as saying. "National and local authorities have been informed and must assist with additional measures at a national level." Cloudflare scrubs botnet domains from global rankingsCloudflare has scrubbed domains associated with the massive AISURU botnet from its top domain rankings. According to security journalist Brian Krebs, AISURU's operators are using the botnet to boost their malicious domain rankings, while simultaneously targeting the company's domain name system (DNS) service. China delivers harsh verdict in cross-border scam crackdownA court in China has sentenced five members of a Myanmar crime syndicate to death for their roles in running industrial-scale scamming compounds near the border with China. The death sentences were handed out to the syndicate boss Bai Suocheng and his son Bai Yingcang, as well as Yang Liqiang, Hu Xiaojiang, and Chen Guangyi. Five others were sentenced to life. In all, 21 members and associates of the syndicate were convicted of fraud, homicide, injury, and other crimes. According to Xinhua, the defendants ran 41 industrial parks to facilitate telecommunications and online fraud at scale. The harsh penalty is the latest in a series of actions governments across the world have taken to combat the rise of cyber-enabled scam centers in Southeast Asia, where thousands are trafficked under the pretext of well-paying jobs, and are trapped, abused, and forced to defraud others in criminal operations worth billions. In September 2025, 11 members of the Ming crime family arrested during a 2023 cross-border crackdown were sentenced to death. Massive global credit card scam busted in €300M stingA coordinated law enforcement operation against a massive credit card fraud scheme dubbed Chargeback has led to the arrest of 18 suspects. The arrested individuals are German, Lithuanian, Dutch, Austrian, Danish, American, and Canadian nationals. "The alleged perpetrators are suspected of setting up an intricate scheme of fake online subscriptions to dating, pornography, and streaming services, among others, which were paid for by credit card," Eurojust said. "Among those arrested are five executive officials from four German payment service providers. The perpetrators deliberately kept monthly credit card payments to their accounts below the maximum of EUR 50 to avoid arousing suspicion among victims about high transfer amounts." The illicit scam is estimated to have defrauded at least €300 million from over 4.3 million credit card users with 19 million accounts in 193 countries between 2016 and 2021. The total value of attempted fraud against card users amounts to more than €750 million. Europol said the suspects used numerous shell companies, primarily registered in the U.K. and Cyprus, to conceal their activities. Every hack or scam has one thing in common — someone takes advantage of trust. As security teams improve their defenses, attackers quickly find new tricks. The best way to stay ahead isn’t to panic, but to stay informed, keep learning, and stay alert. Cybersecurity keeps changing fast — and our understanding needs to keep up.
thehackernews.comNov 6, 2025extracted
Ivanti upgrades Connect Secure with hardened system and gateway improvements
Ivanti upgrades Connect Secure with hardened system and gateway improvements Ivanti released Ivanti Connect Secure (ICS) version 25.X. The update includes a modernized enterprise-grade OS, platform hardening, and gateway enhancements designed to reduce vulnerabilities, shrink attack surfaces, and improve resilience. Enterprise security is central to Connect Secure 25.X. Many legacy software components have been rearchitected with security in mind. These enhancements include a secure web server and Web Application Firewall (WAF), Secure Boot protection, disk encryption, key management, and secure factory reset, to name a few. These features help to secure key aspects of the system, deterring external threats. Connect Secure 25.X utilizes an enterprise-grade Oracle Linux (OL) operating system along with an updated kernel and refreshed tech stack that lays a foundation to deliver scalability and enterprise-grade performance in cloud, virtual and hardware form factors. One of the most impactful security advancements is the hardening of the system using strong Security-Enhanced Linux (SELinux) enforcement, which can limit a threat actor’s abilities within the system. Together, these features deliver comprehensive, layered security designed to meet the evolving needs of today’s enterprise environments. “In the past year, we’ve significantly advanced our Secure by Design strategy—translating our commitment into real action through substantial investments and an expanded security team dedicated to accelerating our initiatives and upholding industry-leading best practices,” said Mike Riemer, Ivanti’s SVP of Network Security Group (NSG) and Field CISO. “This release stands as tangible evidence of our commitment. We listened to our customers, invested in both technology and talent, and modernized the security of Ivanti Connect Secure to provide the resilience and peace of mind our customers expect and deserve,” Riemer continued. Ivanti Connect Secure product enhancements Enable a modernized experience with a new operating system Stability and scalability: The new operating system and its tech stack offer stability and scalability across large deployments, ideal for demanding enterprise environments. Future-ready: Ongoing compatibility with the latest operating systems and third-party features and updates means customers’ systems stay supported. Elevate customers security posture with hardening enhancements Strong enforcement: Connect Secure runs SELinux in “enforcing mode” by default, ensuring that critical system processes are continuously monitored and protected. Attack surface reduction: Connect Secure’s hardening enhancements ensure that the system remains locked down in the face of an active attack, thereby limiting the “blast radius” of such threats. Data protection: Built-in encryption safeguards help prevent data leaks and keep sensitive information secure. Ensure uncompromised performance with gateway enhancements Faster, safer, smarter: The enhanced gateway provides protection against vulnerabilities while maintaining speed and high performance, ensuring that advanced security features do not come at the expense of system performance. At the core of Ivanti’s development philosophy is its Secure Software Development Life Cycle (SSDLC), enabling the seven key elements of Secure Software Design: Security as Code (SaC), Secure by Default, Least Privilege, Separation of Duties (SoD), Minimize Attack Surface Area (ASA), Complete Mediation, and Failing Securely. Additionally, Ivanti also follows their own strict Secure Application Development Standard, which mandates compliance with the OWASP Application Security Verification Standards (ASVS). Together, these frameworks ensure that every product feature is designed and implemented with security as a primary consideration, providing customers with solutions that meet the highest industry benchmarks.
helpnetsecurity.comSep 30, 2025extracted
CL-STA-0969 Installs Covert Malware in Telecom Networks During 10-Month Espionage Campaign
Telecommunications organizations in Southeast Asia have been targeted by a state-sponsored threat actor known as CL-STA-0969 to facilitate remote control over compromised networks. Palo Alto Networks Unit 42 said it observed multiple incidents in the region, including one aimed at critical telecommunications infrastructure between February and November 2024. The attacks are characterized by the use of several tools to enable remote access, as well as the deployment of Cordscan, which can collect location data from mobile devices. However, the cybersecurity company said it found no evidence of data exfiltration from the networks and systems it investigated. Nor were any efforts made by the attackers to track or communicate with target devices within mobile networks. "The threat actor behind CL-STA-0969 maintained high operational security (OPSEC) and employed various defense evasion techniques to avoid detection," security researchers Renzon Cruz, Nicolas Bareil, and Navin Thomas said. CL-STA-0969, per Unit 42, shares significant overlaps with a cluster tracked by CrowdStrike under the name Liminal Panda, a China-nexus espionage group that has been attributed to attacks directed against telecommunications entities in South Asia and Africa since at least 2020 with the goal of intelligence gathering. It's worth noting that some aspects of Liminal Panda's tradecraft were previously attributed to another threat actor called LightBasin (aka UNC1945), which has also singled out the telecom sector since 2016. LightBasin, for its part, overlaps with a third cluster dubbed UNC2891, a financially motivated crew known for its attacks on Automatic Teller Machine (ATM) infrastructure. "While this cluster significantly overlaps with Liminal Panda, we have also observed overlaps in attacker tooling with other reported groups and activity clusters, including Light Basin, UNC3886, UNC2891, and UNC1945," the researchers pointed out. In at least one case, CL-STA-0969 is believed to have employed brute-force attacks against SSH authentication mechanisms for initial compromise, leveraging the access to drop various implants such as - AuthDoor, a malicious Pluggable Authentication Module (PAM) that works similar to SLAPSTICK (originally attributed to UNC1945) to conduct credential theft and provide persistent access to the compromised host via a hard-coded magic password Cordscan, a network scanning and packet capture utility (previously attributed to Liminal Panda) GTPDOOR, a malware explicitly designed to be deployed in telecom networks that are adjacent to GPRS roaming exchanges EchoBackdoor, a passive backdoor that listens for ICMP echo request packets containing command-and-control (C2) instructions to extract the command and send the results of the execution back to the server via an unencrypted ICMP Echo Reply packet Serving GPRS Support Node (SGSN) Emulator (sgsnemu), an emulation software to tunnel traffic via the telecommunications network and bypass firewall restrictions (previously attributed to Liminal Panda) ChronosRAT, a modular ELF binary that's capable of shellcode execution, file operations, keylogging, port forwarding, remote shell, screenshot capture, and proxy capabilities NoDepDNS (internally referred to as MyDns), a Golang backdoor that creates a raw socket and passively listens for UDP traffic on port 53 to parse incoming commands via DNS messages "CL-STA-0969 leveraged different shell scripts that established a reverse SSH tunnel along with other functionalities," Unit 42 researchers noted. "CL-STA-0969 systematically clears logs and deletes executables when they are no longer needed, to maintain a high degree of OPSEC." Adding to the already broad portfolio of malicious tools that the threat actor has deployed are Microsocks proxy, Fast Reverse Proxy (FRP), FScan, Responder, and ProxyChains, as well as programs to exploit flaws in Linux and UNIX-based systems (CVE-2016-5195, CVE-2021-4034, and CVE-2021-3156) to achieve privilege escalation. Besides using a combination of bespoke and publicly available tooling, the threat actors have been found to adopt a number of strategies to fly under the radar. This encompasses DNS tunneling of traffic, routing traffic through compromised mobile operators, erasing authentication logs, disabling Security-Enhanced Linux (SELinux), and disguising process names with convincing names that match the target environment. "CL-STA-0969 demonstrates a deep understanding of telecommunications protocols and infrastructure," Unit 42 said. "Its malware, tools and techniques reveal a calculated effort to maintain persistent, stealthy access. It achieved this by proxying traffic through other telecom nodes, tunneling data using less-scrutinized protocols and employing various defense evasion techniques." China Accuses U.S. Agencies of Targeting Military and Research Institutions The disclosure comes as the National Computer Network Emergency Response Technical Team/Coordination Center of China (CNCERT) accused U.S. intelligence agencies of weaponizing a Microsoft Exchange zero-day exploit to steal defense-related information and hijack more than 50 devices belonging to a "major Chinese military enterprise" between July 2022 and July 2023. The agency also said high-tech military-related universities, scientific research institutes, and enterprises in the country were targeted as part of these attacks to siphon valuable data from compromised hosts. Among those targeted was a Chinese military enterprise in the communications and satellite internet sectors that was attacked from July to November of 2024 by exploiting vulnerabilities in electronic file systems, CNCERT alleged. The attribution effort mirrors tactics from the West, which has repeatedly blamed China for major cyber attacks, counting the latest zero-day exploitation of Microsoft SharePoint Server vulnerabilities. Asked last month about Chinese hacking into U.S. telecom systems and theft of intellectual property on Fox News, U.S. President Donald Trump said, "You don't think we do that to them? We do. We do a lot of things. That's the way the world works. It's a nasty world."
thehackernews.comAug 2, 2025extracted