linux — security advisory
In the Linux kernel, the following vulnerability has been resolved: mm/sparsemem: fix race in accessing memory_section->usage The below race is observed on a PFN which falls into the device memory region with the system memory configuration where PFN's are such that [ZONE_NORMAL ZONE_DEVICE ZONE_NORMAL]. Since normal zone start and end pfn contains the device memory PFN's as well, the compaction triggered will try on the device memory PFN's too though they end up in NOP(because pfn_to_online_page() returns NULL for ZONE_DEVICE memory sections). When from other core, the section mappings are being removed for the ZONE_DEVICE region, that the PFN in question belongs to, on which compaction is currently being operated is resulting into the kernel crash with CONFIG_SPASEMEM_VMEMAP enabled. The crash logs can be seen at [1]. compact_zone() memunmap_pages ------------- --------------- __pageblock_pfn_to_page ...... (a)pfn_valid(): valid_section()//return true (b)__remove_pages()-> sparse_remove_section()-> section_deactivate(): [Free the array ms->usage and set ms->usage = NULL] pfn_section_valid() [Access ms->usage which is NULL] NOTE: From the above it can be said that the race is reduced to between the pfn_valid()/pfn_section_valid() and the section deactivate with SPASEMEM_VMEMAP enabled. The commit b943f045a9af("mm/sparse: fix kernel crash with pfn_section_valid check") tried to address the same problem by clearing the SECTION_HAS_MEM_MAP with the expectation of valid_section(
- Products
- linux
- Affected versions
- 6.1.27-1, 6.1.37-1, 6.1.38-1, 6.1.38-2, 6.1.38-2~bpo11+1, 6.1.38-3, 6.1.38-4, 6.1.38-4~bpo11+1, 6.1.52-1, 6.1.55-1, 6.1.55-1~bpo11+1, 6.1.64-1, 6.1.66-1, 6.1.67-1, 6.1.69-1, 6.1.69-1~bpo11+1, 6.1.76-1~bpo11+1
- Fixed versions
- 6.1.76-1, 6.6.15-1
- CVEs
- CVE-2023-52489
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 1 Nov 2026, 16:00 UTC · Revision 1
Source evidence
In the Linux kernel, the following vulnerability has been resolved: mm/sparsemem: fix race in accessing memory_section->usage The below race is observed on a PFN which falls into the device memory region with the system memory configuration where PFN's are such that [ZONE_NORMAL ZONE_DEVICE ZONE_NORMAL]. Since normal zone start and end pfn contains the device memory PFN's as well, the compaction triggered will try on the device memory PFN's too though they end up in NOP(because pfn_to_online_page() returns NULL for ZONE_DEVICE memory sections). When from other core, the section mappings are being removed for the ZONE_DEVICE region, that the PFN in question belongs to, on which compaction is currently being operated is resulting into the kernel crash with CONFIG_SPASEMEM_VMEMAP enabled. The crash logs can be seen at [1]. compact_zone() memunmap_pages ------------- --------------- __pageblock_pfn_to_page ...... (a)pfn_valid(): valid_section()//return true (b)__remove_pages()-> sparse_remove_section()-> section_deactivate(): [Free the array ms->usage and set ms->usage = NULL] pfn_section_valid() [Access ms->usage which is NULL] NOTE: From the above it can be said that the race is reduced to between the pfn_valid()/pfn_section_valid() and the section deactivate with SPASEMEM_VMEMAP enabled. The commit b943f045a9af("mm/sparse: fix kernel crash with pfn_section_valid check") tried to address the same problem by clearing the SECTION_HAS_MEM_MAP with the expectation of valid_section(
osv:DEBIAN-CVE-2023-52489
linux
Fixed versions: 6.1.76-1
linux
Fixed versions: 6.6.15-1
linux
Fixed versions: 6.6.15-1
Complete source record
{
"id": "dd610915c5ea4da824b3028ba28be16a19b6f5affcea9e68cb3b037e31885366",
"url": "https://osv.dev/vulnerability/DEBIAN-CVE-2023-52489",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "DEBIAN-CVE-2023-52489",
"summary": "In the Linux kernel, the following vulnerability has been resolved: mm/sparsemem: fix race in accessing memory_section->usage The below race is observed on a PFN which falls into the device memory region with the system memory configuration where PFN's are such that [ZONE_NORMAL ZONE_DEVICE ZONE_NORMAL]. Since normal zone start and end pfn contains the device memory PFN's as well, the compaction triggered will try on the device memory PFN's too though they end up in NOP(because pfn_to_online_page() returns NULL for ZONE_DEVICE memory sections). When from other core, the section mappings are being removed for the ZONE_DEVICE region, that the PFN in question belongs to, on which compaction is currently being operated is resulting into the kernel crash with CONFIG_SPASEMEM_VMEMAP enabled. The crash logs can be seen at [1]. compact_zone() memunmap_pages ------------- --------------- __pageblock_pfn_to_page ...... (a)pfn_valid(): valid_section()//return true (b)__remove_pages()-> sparse_remove_section()-> section_deactivate(): [Free the array ms->usage and set ms->usage = NULL] pfn_section_valid() [Access ms->usage which is NULL] NOTE: From the above it can be said that the race is reduced to between the pfn_valid()/pfn_section_valid() and the section deactivate with SPASEMEM_VMEMAP enabled. The commit b943f045a9af(\"mm/sparse: fix kernel crash with pfn_section_valid check\") tried to address the same problem by clearing the SECTION_HAS_MEM_MAP with the expectation of valid_section(",
"evidence": "osv:DEBIAN-CVE-2023-52489",
"products": [
{
"name": {
"value": "linux",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.1.76-1",
"evidence": "/affected/0/ranges"
}
],
"affected_versions": [
{
"value": "6.1.27-1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.37-1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.38-1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.38-2",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.38-2~bpo11+1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.38-3",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.38-4",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.38-4~bpo11+1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.52-1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.55-1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.55-1~bpo11+1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.64-1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.66-1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.67-1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.69-1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.69-1~bpo11+1",
"evidence": "/affected/0/versions"
},
{
"value": "6.1.76-1~bpo11+1",
"evidence": "/affected/0/versions"
}
]
},
{
"name": {
"value": "linux",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.6.15-1",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
},
{
"name": {
"value": "linux",
"evidence": "/affected/2/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.6.15-1",
"evidence": "/affected/2/ranges"
}
],
"affected_versions": []
}
],
"severity": "medium",
"structured": {
"id": "DEBIAN-CVE-2023-52489",
"aliases": [
"DEBIAN-CVE-2023-52489"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H"
}
],
"affected": [
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "6.1.76-1"
}
]
}
],
"package": {
"name": "linux",
"purl": "pkg:deb/debian/linux?arch=source&distro=bookworm",
"ecosystem": "Debian:12"
},
"versions": [
"6.1.27-1",
"6.1.37-1",
"6.1.38-1",
"6.1.38-2",
"6.1.38-2~bpo11+1",
"6.1.38-3",
"6.1.38-4",
"6.1.38-4~bpo11+1",
"6.1.52-1",
"6.1.55-1",
"6.1.55-1~bpo11+1",
"6.1.64-1",
"6.1.66-1",
"6.1.67-1",
"6.1.69-1",
"6.1.69-1~bpo11+1",
"6.1.76-1~bpo11+1"
],
"database_specific": {
"source": "https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2023-52489.json"
},
"ecosystem_specific": {
"urgency": "not yet assigned"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "6.6.15-1"
}
]
}
],
"package": {
"name": "linux",
"purl": "pkg:deb/debian/linux?arch=source&distro=trixie",
"ecosystem": "Debian:13"
},
"database_specific": {
"source": "https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2023-52489.json"
},
"ecosystem_specific": {
"urgency": "not yet assigned"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "6.6.15-1"
}
]
}
],
"package": {
"name": "linux",
"purl": "pkg:deb/debian/linux?arch=source&distro=forky",
"ecosystem": "Debian:14"
},
"database_specific": {
"source": "https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2023-52489.json"
},
"ecosystem_specific": {
"urgency": "not yet assigned"
}
}
],
"modified": "2026-10-26T18:02:36.151694657Z",
"provider": "osv",
"upstream": [
"CVE-2023-52489"
],
"references": [
"https://security-tracker.debian.org/tracker/CVE-2023-52489"
]
},
"related_cves": [
{
"value": "CVE-2023-52489",
"evidence": "/upstream"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 456342,
"published_at": "2024-03-11T18:15:16.673+00:00"
}