xfs: fix wild memcpy access when formatting ondisk rtrefcount btree roots
In the Linux kernel, the following vulnerability has been resolved: xfs: fix wild memcpy access when formatting ondisk rtrefcount btree roots LOLLM noticed that the inode btree root formatting methods copy too many bytes -- there's only one set of keys in node blocks, not two. This causes memory corruption of whatever's beyond the buffers.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.18.55, 7.2.9
- CVEs
- CVE-2026-98447
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 7 Nov 2026, 02:01 UTC · Revision 1
Source evidence
xfs: fix wild memcpy access when formatting ondisk rtrefcount btree roots
core-osv · Original sourcePublished 18 Oct 2026, 15:14 UTC
In the Linux kernel, the following vulnerability has been resolved: xfs: fix wild memcpy access when formatting ondisk rtrefcount btree roots LOLLM noticed that the inode btree root formatting methods copy too many bytes -- there's only one set of keys in node blocks, not two. This causes memory corruption of whatever's beyond the buffers.
osv:CVE-2026-98447
Kernel
Fixed versions: 6.18.55, 7.2.9
Complete source record
{
"id": "0d56bda424ac29ec92e39b452a38ab5aa64672e9b264d7b2de6fff140abf996a",
"url": "https://osv.dev/vulnerability/CVE-2026-98447",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "xfs: fix wild memcpy access when formatting ondisk rtrefcount btree roots",
"summary": "In the Linux kernel, the following vulnerability has been resolved: xfs: fix wild memcpy access when formatting ondisk rtrefcount btree roots LOLLM noticed that the inode btree root formatting methods copy too many bytes -- there's only one set of keys in node blocks, not two. This causes memory corruption of whatever's beyond the buffers.",
"evidence": "osv:CVE-2026-98447",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.18.55",
"evidence": "/affected/1/ranges"
},
{
"value": "7.2.9",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2026-98447",
"aliases": [
"CVE-2026-98447"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "f0415af60f482a2192065be8b334b409495ca8a3"
},
{
"fixed": "d46492fb8018d12d00651b06b9d240e747110b38"
},
{
"fixed": "2703b954d306ebfe3b11e33e259759329c11b690"
},
{
"fixed": "fe2f9135df43db849e74f03956d322ac20b59af7"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-98447.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.14.0"
},
{
"fixed": "6.18.55"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.2.9"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-98447.json"
}
}
],
"modified": "2026-10-28T02:30:48.881534958Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/2703b954d306ebfe3b11e33e259759329c11b690",
"https://git.kernel.org/stable/c/d46492fb8018d12d00651b06b9d240e747110b38",
"https://git.kernel.org/stable/c/fe2f9135df43db849e74f03956d322ac20b59af7",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/98xxx/CVE-2026-98447.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-98447",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/98xxx/CVE-2026-98447.json"
}
},
"related_cves": [
{
"value": "CVE-2026-98447",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 517193,
"published_at": "2026-10-18T15:14:57.561+00:00"
}