Answer in brief
CVE-2023-54062 records a High severity (CVSS 7.8) vulnerability in ext4: fix invalid free tracking in ext4_xattr_move_to_block(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2023-54062 records a High severity (CVSS 7.8) vulnerability in ext4: fix invalid free tracking in ext4_xattr_move_to_block(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=c7851208abffe5ae4deb01cf48763911dc14fc67 <76887be2a96193cd11be818551b8934ecdb3123f || >=f5cdc6a7339f250d44d4d469ed7a474ac0d6c7a7 <f30f3391d089dc91aef91d08f4b04a6c0df2b067 || >=3b28c799a1334adb5a19f42f03abe0d8cbb05938 <ba04d6af5ac440a6d5a2d35dc1d8e2cb0323550a || >=d738789ae9ec47d3458a008788f3cdc862ebf0cb <1a8822343e67432b658145d2760a524c884da9d4 || >=a6744e14ce7045ab1a728bde9595f62fbd39f1d2 <8beaa3cb293a8f7bacf711cf52201d59859dbc40 || >=8b6d06b3be7648b3b0f428558293ddf6e2cb94bf <c5fa4eedddd1c8342ce533cb401c0e693e55b4e3 || >=d2efaf8c870c7067b8d1779773134f3481cd8f68 <a18670395e5f28acddeca037c5e4bd2ea961b70a || >=1e9d62d252812575ded7c620d8fc67c32ff06c16 <b2fab1807d26acd1c6115b95b5eddd697d84751b || >=1e9d62d252812575ded7c620d8fc67c32ff06c16 <b87c7cdf2bed4928b899e1ce91ef0d147017ba45 || >=4.14.308 <4.14.315 || >=4.19.276 <4.19.283 || >=5.4.235 <5.4.243 || >=5.10.173 <5.10.180 || >=5.15.99 <5.15.112 || >=6.1.16 <6.1.29 || >=6.2.3 <6.2.16 | 76887be2a96193cd11be818551b8934ecdb3123f, f30f3391d089dc91aef91d08f4b04a6c0df2b067, ba04d6af5ac440a6d5a2d35dc1d8e2cb0323550a, 1a8822343e67432b658145d2760a524c884da9d4, 8beaa3cb293a8f7bacf711cf52201d59859dbc40, c5fa4eedddd1c8342ce533cb401c0e693e55b4e3, a18670395e5f28acddeca037c5e4bd2ea961b70a, b2fab1807d26acd1c6115b95b5eddd697d84751b, b87c7cdf2bed4928b899e1ce91ef0d147017ba45, 4.14.315, 4.19.283, 5.4.243, 5.10.180, 5.15.112, 6.1.29, 6.2.16 |
| Linux/Linuxgeneric | 6.3 | Not reported |
Published upstream
Dec 24, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
In the Linux kernel, the following vulnerability has been resolved: ext4: fix invalid free tracking in ext4_xattr_move_to_block() In ext4_xattr_move_to_block(), the value of the extended attribute which we need to move to an external block may be allocated by kvmalloc() if the value is stored in an external inode. So at the end of the function the code tried to check if this was the case by testing entry->e_value_inum. However, at this point, the pointer to the xattr entry is no longer valid, because it was removed from the original location where it had been stored. So we could end up calling kvfree() on a pointer which was not allocated by kvmalloc(); or we could also potentially leak memory by not freeing the buffer when it should be freed. Fix this by storing whether it should be freed in a separate variable.
Quoted source text, attributed separately from HOL analysis.
CVSS is 7.8. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=c7851208abffe5ae4deb01cf48763911dc14fc67 <76887be2a96193cd11be818551b8934ecdb3123f || >=f5cdc6a7339f250d44d4d469ed7a474ac0d6c7a7 <f30f3391d089dc91aef91d08f4b04a6c0df2b067 || >=3b28c799a1334adb5a19f42f03abe0d8cbb05938 <ba04d6af5ac440a6d5a2d35dc1d8e2cb0323550a || >=d738789ae9ec47d3458a008788f3cdc862ebf0cb <1a8822343e67432b658145d2760a524c884da9d4 || >=a6744e14ce7045ab1a728bde9595f62fbd39f1d2 <8beaa3cb293a8f7bacf711cf52201d59859dbc40 || >=8b6d06b3be7648b3b0f428558293ddf6e2cb94bf <c5fa4eedddd1c8342ce533cb401c0e693e55b4e3 || >=d2efaf8c870c7067b8d1779773134f3481cd8f68 <a18670395e5f28acddeca037c5e4bd2ea961b70a || >=1e9d62d252812575ded7c620d8fc67c32ff06c16 <b2fab1807d26acd1c6115b95b5eddd697d84751b || >=1e9d62d252812575ded7c620d8fc67c32ff06c16 <b87c7cdf2bed4928b899e1ce91ef0d147017ba45 || >=4.14.308 <4.14.315 || >=4.19.276 <4.19.283 || >=5.4.235 <5.4.243 || >=5.10.173 <5.10.180 || >=5.15.99 <5.15.112 || >=6.1.16 <6.1.29 || >=6.2.3 <6.2.16 | 76887be2a96193cd11be818551b8934ecdb3123f, f30f3391d089dc91aef91d08f4b04a6c0df2b067, ba04d6af5ac440a6d5a2d35dc1d8e2cb0323550a, 1a8822343e67432b658145d2760a524c884da9d4, 8beaa3cb293a8f7bacf711cf52201d59859dbc40, c5fa4eedddd1c8342ce533cb401c0e693e55b4e3, a18670395e5f28acddeca037c5e4bd2ea961b70a, b2fab1807d26acd1c6115b95b5eddd697d84751b, b87c7cdf2bed4928b899e1ce91ef0d147017ba45, 4.14.315, 4.19.283, 5.4.243, 5.10.180, 5.15.112, 6.1.29, 6.2.16 |
| Linux/Linuxgeneric | 6.3 | Not reported |
Published upstream
Dec 24, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 4, 2026
In the Linux kernel, the following vulnerability has been resolved: ext4: fix invalid free tracking in ext4_xattr_move_to_block() In ext4_xattr_move_to_block(), the value of the extended attribute which we need to move to an external block may be allocated by kvmalloc() if the value is stored in an external inode. So at the end of the function the code tried to check if this was the case by testing entry->e_value_inum. However, at this point, the pointer to the xattr entry is no longer valid, because it was removed from the original location where it had been stored. So we could end up calling kvfree() on a pointer which was not allocated by kvmalloc(); or we could also potentially leak memory by not freeing the buffer when it should be freed. Fix this by storing whether it should be freed in a separate variable.
Quoted source text, attributed separately from HOL analysis.