🛡️ CVE-2024-49873 on Ubuntu — linux-allwinner-5.19
Description
In the Linux kernel, the following vulnerability has been resolved: mm/filemap: fix filemap_get_folios_contig THP panic Patch series "memfd-pin huge page fixes". Fix multiple bugs that occur when using memfd_pin_folios with hugetlb pages and THP. The hugetlb bugs only bite when the page is not yet faulted in when memfd_pin_folios is called. The THP bug bites when the starting offset passed to memfd_pin_folios is not huge page aligned. See the commit messages for details. This patch (of 5): memfd_pin_folios on memory backed by THP panics if the requested start offset is not huge page aligned: BUG: kernel NULL pointer dereference, address: 0000000000000036 RIP: 0010:filemap_get_folios_contig+0xdf/0x290 RSP: 0018:ffffc9002092fbe8 EFLAGS: 00010202 RAX: 0000000000000002 RBX: 0000000000000002 RCX: 0000000000000002 The fault occurs here, because xas_load returns a folio with value 2: filemap_get_folios_contig() for (folio = xas_load(&xas); folio && xas.xa_index <= end; folio = xas_next(&xas)) { ... if (!folio_try_get(folio)) <-- BOOM "2" is an xarray sibling entry. We get it because memfd_pin_folios does not round the indices passed to filemap_get_folios_contig to huge page boundaries for THP, so we load from the middle of a huge page range see a sibling. (It does round for hugetlbfs, at the is_file_hugepages test). To fix, if the folio is a sibling, then return the next index as the starting point for the next call to filemap_get_folios_contig.
Distribution advisory
This page covers CVE-2024-49873 as tracked by Ubuntu, for the package linux-allwinner-5.19. The fix is available in version 6.11.0-1015.15; earlier versions remain affected.
How this vulnerability can be exploited
This issue can be reached with local access to the system, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality none, integrity none, availability high.
CVSS metrics in full
The score comes from this vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- Attack vector: Local — a local account, shell or session on the host is needed.
- Attack complexity: Low — the attack works reliably, with no preparation.
- Privileges required: Low — an ordinary user account is enough.
- User interaction: None — nobody has to be tricked into anything.
- Scope: Unchanged — the damage stays inside the vulnerable component.
- Confidentiality impact: None.
- Integrity impact: None.
- Availability impact: High — total loss, or loss the attacker controls.
Affected software
UBUNTU-CVE-2024-49873 is recorded against 76 packages.
- linux-allwinner-5.19
- linux-aws-5.0
- linux-aws-5.11
- linux-aws-5.13
- linux-aws-5.19
- linux-aws-5.3
- linux-aws-5.8
- linux-aws-6.2
- linux-aws-6.5
- linux-azure
- linux-azure-5.11
- linux-azure-5.13
- linux-azure-5.19
- linux-azure-5.3
- linux-azure-5.8
- linux-azure-6.2
- linux-azure-6.5
- linux-azure-edge
- linux-azure-fde
- linux-azure-fde-5.19
- linux-azure-fde-6.2
- linux-gcp
- linux-gcp-5.11
- linux-gcp-5.13
Show the remaining 52 packages
- linux-gcp-5.19
- linux-gcp-5.3
- linux-gcp-5.8
- linux-gcp-6.2
- linux-gcp-6.5
- linux-gke
- linux-gke-4.15
- linux-gke-5.15
- linux-gke-5.4
- linux-gkeop-5.4
- linux-hwe
- linux-hwe-5.11
- linux-hwe-5.13
- linux-hwe-5.19
- linux-hwe-5.8
- linux-hwe-6.2
- linux-hwe-6.5
- linux-hwe-edge
- linux-intel-5.13
- linux-intel-iot-realtime
- linux-lowlatency-hwe-5.19
- linux-lowlatency-hwe-6.2
- linux-lowlatency-hwe-6.5
- linux-nvidia-6.2
- linux-nvidia-6.5
- linux-oem
- linux-oem-5.10
- linux-oem-5.13
- linux-oem-5.14
- linux-oem-5.17
- linux-oem-5.6
- linux-oem-6.0
- linux-oem-6.1
- linux-oem-6.11 (fixed in 6.11.0-1015.15)
- linux-oem-6.5
- linux-oracle-5.0
- linux-oracle-5.11
- linux-oracle-5.13
- linux-oracle-5.3
- linux-oracle-5.8
- linux-oracle-6.5
- linux-raspi-realtime
- linux-raspi2
- linux-realtime
- linux-riscv
- linux-riscv-5.11
- linux-riscv-5.19
- linux-riscv-5.8
- linux-riscv-6.5
- linux-starfive-5.19
- linux-starfive-6.2
- linux-starfive-6.5
Timeline and source
Published on 21 October 2024 and last revised on 4 February 2026. No public exploit is currently recorded for this entry. Record sourced from OSV.
References
ubuntu.com (Report)
www.cve.org (Report)
git.kernel.org (Report)
git.kernel.org (Report)
git.kernel.org (Report)
ubuntu.com (Advisory)
ubuntu.com (Advisory)
ubuntu.com (Advisory)
Other advisories for this package
linux-allwinner-5.19 has other advisories on record. If you are patching this one, these are worth checking on the same host:
- UBUNTU-CVE-2022-4994 (published 30 Jul 2026)
- UBUNTU-CVE-2023-20585 (published 16 Apr 2026)
- UBUNTU-CVE-2022-50816 (published 30 Dec 2025)
- UBUNTU-CVE-2022-50849 (published 30 Dec 2025)
- UBUNTU-CVE-2022-50881 (published 30 Dec 2025)
- UBUNTU-CVE-2022-50836 (published 30 Dec 2025)
- UBUNTU-CVE-2022-50868 (published 30 Dec 2025)
- UBUNTU-CVE-2022-50822 (published 30 Dec 2025)
CVE-2024-49873 on other distributions
Each distribution ships its own build and its own fixed version. Pick the one you run:
Details
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| linux-allwinner-5.19 | — | — |
| linux-aws-5.0 | — | — |
| linux-aws-5.11 | — | — |
| linux-aws-5.13 | — | — |
| linux-aws-5.19 | — | — |
| linux-aws-5.3 | — | — |
| linux-aws-5.8 | — | — |
| linux-aws-6.2 | — | — |
| linux-aws-6.5 | — | — |
| linux-azure | — | — |
| linux-azure-5.11 | — | — |
| linux-azure-5.13 | — | — |
| linux-azure-5.19 | — | — |
| linux-azure-5.3 | — | — |
| linux-azure-5.8 | — | — |
| linux-azure-6.2 | — | — |
| linux-azure-6.5 | — | — |
| linux-azure-edge | — | — |
| linux-azure-fde | — | — |
| linux-azure-fde-5.19 | — | — |
| linux-azure-fde-6.2 | — | — |
| linux-gcp | — | — |
| linux-gcp-5.11 | — | — |
| linux-gcp-5.13 | — | — |
| linux-gcp-5.19 | — | — |
| linux-gcp-5.3 | — | — |
| linux-gcp-5.8 | — | — |
| linux-gcp-6.2 | — | — |
| linux-gcp-6.5 | — | — |
| linux-gke | — | — |
| linux-gke-4.15 | — | — |
| linux-gke-5.15 | — | — |
| linux-gke-5.4 | — | — |
| linux-gkeop-5.4 | — | — |
| linux-hwe | — | — |
| linux-hwe-5.11 | — | — |
| linux-hwe-5.13 | — | — |
| linux-hwe-5.19 | — | — |
| linux-hwe-5.8 | — | — |
| linux-hwe-6.2 | — | — |
| linux-hwe-6.5 | — | — |
| linux-hwe-edge | — | — |
| linux-intel-5.13 | — | — |
| linux-intel-iot-realtime | — | — |
| linux-lowlatency-hwe-5.19 | — | — |
| linux-lowlatency-hwe-6.2 | — | — |
| linux-lowlatency-hwe-6.5 | — | — |
| linux-nvidia-6.2 | — | — |
| linux-nvidia-6.5 | — | — |
| linux-oem | — | — |
| linux-oem-5.10 | — | — |
| linux-oem-5.13 | — | — |
| linux-oem-5.14 | — | — |
| linux-oem-5.17 | — | — |
| linux-oem-5.6 | — | — |
| linux-oem-6.0 | — | — |
| linux-oem-6.1 | — | — |
| linux-oem-6.11 | — | 6.11.0-1015.15 |
| linux-oem-6.5 | — | — |
| linux-oracle-5.0 | — | — |
| linux-oracle-5.11 | — | — |
| linux-oracle-5.13 | — | — |
| linux-oracle-5.3 | — | — |
| linux-oracle-5.8 | — | — |
| linux-oracle-6.5 | — | — |
| linux-raspi-realtime | — | — |
| linux-raspi2 | — | — |
| linux-realtime | — | — |
| linux-riscv | — | — |
| linux-riscv-5.11 | — | — |
| linux-riscv-5.19 | — | — |
| linux-riscv-5.8 | — | — |
| linux-riscv-6.5 | — | — |
| linux-starfive-5.19 | — | — |
| linux-starfive-6.2 | — | — |
| linux-starfive-6.5 | — | — |
References
Similar Threats
- Unknown UBUNTU-CVE-2016-20022
- Unknown UBUNTU-CVE-2020-36778
- Unknown UBUNTU-CVE-2020-36779
- Unknown UBUNTU-CVE-2020-36780
- Unknown UBUNTU-CVE-2020-36781
Vulnerability Monitoring
Track new vulnerabilities in linux-allwinner-5.19
UBUNTU-CVE-2024-49873 is rated CVSS 5.5 Medium. BotEraser monitors your WordPress installation and notifies you when software you use appears in our vulnerability database.
Set Up Free Alerts →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.
