USN-7288-1: Linux kernel vulnerabilities

Published Feb 24, 2025
·
Updated

Attila Szász discovered that the HFS+ file system implementation in the Linux Kernel contained a heap overflow vulnerability. An attacker could use a specially crafted file system image that, when mounted, could cause a denial of service (system crash) or possibly execute arbitrary code. (CVE-2025-0927)

Several security issues were discovered in the Linux kernel. An attacker could possibly use these to compromise the system. This update corrects flaws in the following subsystems: - ARM64 architecture; - x86 architecture; - Block layer subsystem; - ACPI drivers; - GPU drivers; - HID subsystem; - I2C subsystem; - IIO ADC drivers; - IIO subsystem; - InfiniBand drivers; - IOMMU subsystem; - IRQ chip drivers; - Multiple devices driver; - Media drivers; - Network drivers; - STMicroelectronics network drivers; - Parport drivers; - Pin controllers subsystem; - Direct Digital Synthesis drivers; - TCM subsystem; - TTY drivers; - USB Dual Role (OTG-ready) Controller drivers; - USB Serial drivers; - USB Type-C support driver; - USB Type-C Connector System Software Interface driver; - BTRFS file system; - File systems infrastructure; - Network file system (NFS) client; - NILFS2 file system; - NTFS3 file system; - SMB network file system; - User-space API (UAPI); - iouring subsystem; - BPF subsystem; - Timer substystem drivers; - Tracing infrastructure; - Closures library; - Memory management; - Amateur Radio drivers; - Bluetooth subsystem; - Networking core; - IPv4 networking; - MAC80211 subsystem; - Multipath TCP; - Netfilter; - Network traffic control; - SCTP protocol; - XFRM subsystem; - Key management; - FireWire sound drivers; - HD-audio driver; - QCOM ASoC drivers; - STMicroelectronics SoC drivers; - KVM core; (CVE-2024-50202, CVE-2024-50208, CVE-2024-50265, CVE-2024-41080, CVE-2024-50101, CVE-2024-39497, CVE-2024-50153, CVE-2024-50162, CVE-2024-50150, CVE-2024-50115, CVE-2024-53066, CVE-2024-50279, CVE-2024-50116, CVE-2024-50218, CVE-2024-53104, CVE-2024-50086, CVE-2024-50154, CVE-2024-50244, CVE-2024-50074, CVE-2024-50278, CVE-2024-50262, CVE-2024-50168, CVE-2024-50134, CVE-2024-53063, CVE-2024-50236, CVE-2024-50082, CVE-2024-50234, CVE-2024-50247, CVE-2024-50282, CVE-2024-50267, CVE-2024-40965, CVE-2024-50229, CVE-2024-50110, CVE-2024-35887, CVE-2024-50302, CVE-2024-50036, CVE-2024-50209, CVE-2024-50287, CVE-2024-50245, CVE-2024-50072, CVE-2024-50301, CVE-2024-50201, CVE-2024-53097, CVE-2024-40953, CVE-2024-50085, CVE-2024-50299, CVE-2024-50292, CVE-2024-50269, CVE-2024-50182, CVE-2024-50233, CVE-2024-53088, CVE-2024-50259, CVE-2024-50232, CVE-2024-53055, CVE-2024-50195, CVE-2024-50273, CVE-2024-42291, CVE-2024-50192, CVE-2024-50251, CVE-2024-50193, CVE-2024-50142, CVE-2024-53101, CVE-2024-50205, CVE-2024-26718, CVE-2024-50167, CVE-2024-50010, CVE-2024-50230, CVE-2024-41066, CVE-2024-50194, CVE-2024-50148, CVE-2024-50151, CVE-2024-50127, CVE-2024-50160, CVE-2023-52913, CVE-2024-53052, CVE-2024-50156, CVE-2024-50141, CVE-2024-50103, CVE-2024-50296, CVE-2024-50257, CVE-2024-50199, CVE-2024-50128, CVE-2024-50058, CVE-2024-50099, CVE-2024-50290, CVE-2024-53042, CVE-2024-50295, CVE-2024-50268, CVE-2024-50163, CVE-2024-53058, CVE-2024-50185, CVE-2024-50117, CVE-2024-50237, CVE-2024-50083, CVE-2024-50131, CVE-2024-50196, CVE-2024-42252, CVE-2024-50143, CVE-2024-50171, CVE-2024-50249, CVE-2024-53059, CVE-2024-50198, CVE-2024-53061)

Affected Software

39 affected componentsFixes available
Ubuntu Linux kernel
All of the following
ubuntu/linux-image-5.15.0-133-generic<5.15.0-133.144
5.15.0-133.144
Ubuntu Ubuntu=22.04
All of the following
ubuntu/linux-image-5.15.0-133-generic-64k<5.15.0-133.144
5.15.0-133.144
Ubuntu Ubuntu=22.04
All of the following
ubuntu/linux-image-5.15.0-133-generic-lpae<5.15.0-133.144
5.15.0-133.144
Ubuntu Ubuntu=22.04
All of the following
ubuntu/linux-image-5.15.0-133-lowlatency<5.15.0-133.143
5.15.0-133.143
Ubuntu Ubuntu=22.04
All of the following
ubuntu/linux-image-5.15.0-133-lowlatency-64k<5.15.0-133.143
5.15.0-133.143
Ubuntu Ubuntu=22.04
All of the following
ubuntu/linux-image-generic<5.15.0.133.132
5.15.0.133.132
Ubuntu Ubuntu=22.04
All of the following
ubuntu/linux-image-generic-64k<5.15.0.133.132
5.15.0.133.132
Ubuntu Ubuntu=22.04
All of the following
ubuntu/linux-image-generic-64k-hwe-20.04<5.15.0.133.132
5.15.0.133.132
Ubuntu Ubuntu=22.04
All of the following
ubuntu/linux-image-generic-hwe-20.04<5.15.0.133.132
5.15.0.133.132
Ubuntu Ubuntu=22.04
All of the following
ubuntu/linux-image-generic-lpae<5.15.0.133.132
5.15.0.133.132
Ubuntu Ubuntu=22.04
All of the following
ubuntu/linux-image-generic-lpae-hwe-20.04<5.15.0.133.132
5.15.0.133.132
Ubuntu Ubuntu=22.04
All of the following
ubuntu/linux-image-lowlatency<5.15.0.133.120
5.15.0.133.120
Ubuntu Ubuntu=22.04
All of the following
ubuntu/linux-image-lowlatency-64k<5.15.0.133.120
5.15.0.133.120
Ubuntu Ubuntu=22.04
All of the following
ubuntu/linux-image-lowlatency-64k-hwe-20.04<5.15.0.133.120
5.15.0.133.120
Ubuntu Ubuntu=22.04
All of the following
ubuntu/linux-image-lowlatency-hwe-20.04<5.15.0.133.120
5.15.0.133.120
Ubuntu Ubuntu=22.04
All of the following
ubuntu/linux-image-oem-20.04<5.15.0.133.132
5.15.0.133.132
Ubuntu Ubuntu=22.04
All of the following
ubuntu/linux-image-virtual<5.15.0.133.132
5.15.0.133.132
Ubuntu Ubuntu=22.04
All of the following
ubuntu/linux-image-virtual-hwe-20.04<5.15.0.133.132
5.15.0.133.132
Ubuntu Ubuntu=22.04
ubuntu/linux<5.15.0-133.144
5.15.0-133.144
ubuntu/linux-lowlatency<5.15.0-133.143
5.15.0-133.143

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade ubuntu/linux-image-5.15.0-133-generic to a version that resolves this vulnerability.

    Fixed in 5.15.0-133.144
  2. Upgrade

    Upgrade ubuntu/linux-image-5.15.0-133-generic-64k to a version that resolves this vulnerability.

    Fixed in 5.15.0-133.144
  3. Upgrade

    Upgrade ubuntu/linux-image-5.15.0-133-generic-lpae to a version that resolves this vulnerability.

    Fixed in 5.15.0-133.144
  4. Upgrade

    Upgrade ubuntu/linux-image-5.15.0-133-lowlatency to a version that resolves this vulnerability.

    Fixed in 5.15.0-133.143
  5. Upgrade

    Upgrade ubuntu/linux-image-5.15.0-133-lowlatency-64k to a version that resolves this vulnerability.

    Fixed in 5.15.0-133.143
  6. Upgrade

    Upgrade ubuntu/linux-image-generic to a version that resolves this vulnerability.

    Fixed in 5.15.0.133.132
  7. Upgrade

    Upgrade ubuntu/linux-image-generic-64k to a version that resolves this vulnerability.

    Fixed in 5.15.0.133.132
  8. Upgrade

    Upgrade ubuntu/linux-image-generic-64k-hwe-20.04 to a version that resolves this vulnerability.

    Fixed in 5.15.0.133.132
  9. Upgrade

    Upgrade ubuntu/linux-image-generic-hwe-20.04 to a version that resolves this vulnerability.

    Fixed in 5.15.0.133.132
  10. Upgrade

    Upgrade ubuntu/linux-image-generic-lpae to a version that resolves this vulnerability.

    Fixed in 5.15.0.133.132
  11. Upgrade

    Upgrade ubuntu/linux-image-generic-lpae-hwe-20.04 to a version that resolves this vulnerability.

    Fixed in 5.15.0.133.132
  12. Upgrade

    Upgrade ubuntu/linux-image-lowlatency to a version that resolves this vulnerability.

    Fixed in 5.15.0.133.120
  13. Upgrade

    Upgrade ubuntu/linux-image-lowlatency-64k to a version that resolves this vulnerability.

    Fixed in 5.15.0.133.120
  14. Upgrade

    Upgrade ubuntu/linux-image-lowlatency-64k-hwe-20.04 to a version that resolves this vulnerability.

    Fixed in 5.15.0.133.120
  15. Upgrade

    Upgrade ubuntu/linux-image-lowlatency-hwe-20.04 to a version that resolves this vulnerability.

    Fixed in 5.15.0.133.120
  16. Upgrade

    Upgrade ubuntu/linux-image-oem-20.04 to a version that resolves this vulnerability.

    Fixed in 5.15.0.133.132
  17. Upgrade

    Upgrade ubuntu/linux-image-virtual to a version that resolves this vulnerability.

    Fixed in 5.15.0.133.132
  18. Upgrade

    Upgrade ubuntu/linux-image-virtual-hwe-20.04 to a version that resolves this vulnerability.

    Fixed in 5.15.0.133.132
  19. Upgrade

    Upgrade ubuntu/linux to a version that resolves this vulnerability.

    Fixed in 5.15.0-133.144
  20. Upgrade

    Upgrade ubuntu/linux-lowlatency to a version that resolves this vulnerability.

    Fixed in 5.15.0-133.143
  21. Upgrade

    Upgrade Linux kernel to a version that resolves this vulnerability.

    Patch USN-7288-1

Event History

Feb 24, 2025
Advisory Published
via Ubuntu·12:00 AM
Data Sourced
via Ubuntu·12:00 AM
DescriptionAffected Software
Advisory Published
via OSV·05:45 PM
Data Sourced
via OSV·05:45 PM
DescriptionAffected Software

Child vulnerabilities

Contains the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of USN-7288-1?

The USN-7288-1 vulnerability has a high severity level due to the potential for denial of service or arbitrary code execution.

2

How do I fix USN-7288-1?

To fix USN-7288-1, update to the patched kernel version 5.15.0-133.144 or later for your affected Ubuntu system.

3

What systems are affected by USN-7288-1?

USN-7288-1 affects Ubuntu 22.04 systems utilizing specific Linux kernel packages.

4

What type of vulnerability is USN-7288-1?

USN-7288-1 is a heap overflow vulnerability found in the HFS+ file system implementation of the Linux Kernel.

5

Can USN-7288-1 lead to system crashes?

Yes, USN-7288-1 can cause system crashes if an attacker mounts a specially crafted file system image.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203