Answer in brief
CVE-2024-26926 records a Unknown severity vulnerability in binder: check offset alignment in binder_get_object(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), linux/linux_kernel (generic), linux/linux_kernel (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-2024-26926 records a Unknown severity vulnerability in binder: check offset alignment in binder_get_object(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), linux/linux_kernel (generic), linux/linux_kernel (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. 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), linux/linux_kernel (generic), linux/linux_kernel (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=c056a6ba35e00ae943e377eb09abd77a6915b31a <68a28f551e4690db2b27b3db716c7395f6fada12 || >=23e9d815fad84c1bee3742a8de4bd39510435362 <48a1f83ca9c68518b1a783c62e6a8223144fa9fc || >=7a9ad4aceb0226b391c9d3b8e4ac2e7d438b6bde <a2fd6dbc98be1105a1d8e9e31575da8873ef115c || >=6d98eb95b450a75adb4516a1d33652dc78d2b20c <a6d2a8b211c874971ee4cf3ddd167408177f6e76 || >=6d98eb95b450a75adb4516a1d33652dc78d2b20c <1d7f1049035b2060342f11eff957cf567d810bdc || >=6d98eb95b450a75adb4516a1d33652dc78d2b20c <f01d6619045704d78613b14e2e0420bfdb7f1c15 || >=6d98eb95b450a75adb4516a1d33652dc78d2b20c <aaef73821a3b0194a01bd23ca77774f704a04d40 || 66e12f5b3a9733f941893a00753b10498724607d || >=5.4.226 <5.4.275 || >=5.10.157 <5.10.216 || >=5.15.17 <5.15.157 || >=5.16.3 <5.17 | 68a28f551e4690db2b27b3db716c7395f6fada12, 48a1f83ca9c68518b1a783c62e6a8223144fa9fc, a2fd6dbc98be1105a1d8e9e31575da8873ef115c, a6d2a8b211c874971ee4cf3ddd167408177f6e76, 1d7f1049035b2060342f11eff957cf567d810bdc, f01d6619045704d78613b14e2e0420bfdb7f1c15, aaef73821a3b0194a01bd23ca77774f704a04d40, 5.4.275, 5.10.216, 5.15.157, 5.17 |
| Linux/Linuxgeneric | 5.17 | Not reported |
| linux/linux_kernelgeneric | >=c056a6ba35e0 <68a28f551e46 || >=23e9d815fad8 <48a1f83ca9c6 || >=7a9ad4aceb02 <a2fd6dbc98be || >=6d98eb95b450 <a6d2a8b211c8 || >=6d98eb95b450 <1d7f1049035b || >=6d98eb95b450 <f01d66190457 || >=6d98eb95b450 <aaef73821a3b | 68a28f551e46, 48a1f83ca9c6, a2fd6dbc98be, a6d2a8b211c8, 1d7f1049035b, f01d66190457, aaef73821a3b |
| linux/linux_kernelgeneric | 5.17 | Not reported |
Published upstream
Apr 24, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: binder: check offset alignment in binder_get_object() Commit 6d98eb95b450 ("binder: avoid potential data leakage when copying txn") introduced changes to how binder objects are copied. In doing so, it unintentionally removed an offset alignment check done through calls to binder_alloc_copy_from_buffer() -> check_buffer(). These calls were replaced in binder_get_object() with copy_from_user(), so now an explicit offset alignment check is needed here. This avoids later complications when unwinding the objects gets harder. It is worth noting this check existed prior to commit 7a67a39320df ("binder: add function to copy binder object from buffer"), likely removed due to redundancy at the time.
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. 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), linux/linux_kernel (generic), linux/linux_kernel (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=c056a6ba35e00ae943e377eb09abd77a6915b31a <68a28f551e4690db2b27b3db716c7395f6fada12 || >=23e9d815fad84c1bee3742a8de4bd39510435362 <48a1f83ca9c68518b1a783c62e6a8223144fa9fc || >=7a9ad4aceb0226b391c9d3b8e4ac2e7d438b6bde <a2fd6dbc98be1105a1d8e9e31575da8873ef115c || >=6d98eb95b450a75adb4516a1d33652dc78d2b20c <a6d2a8b211c874971ee4cf3ddd167408177f6e76 || >=6d98eb95b450a75adb4516a1d33652dc78d2b20c <1d7f1049035b2060342f11eff957cf567d810bdc || >=6d98eb95b450a75adb4516a1d33652dc78d2b20c <f01d6619045704d78613b14e2e0420bfdb7f1c15 || >=6d98eb95b450a75adb4516a1d33652dc78d2b20c <aaef73821a3b0194a01bd23ca77774f704a04d40 || 66e12f5b3a9733f941893a00753b10498724607d || >=5.4.226 <5.4.275 || >=5.10.157 <5.10.216 || >=5.15.17 <5.15.157 || >=5.16.3 <5.17 | 68a28f551e4690db2b27b3db716c7395f6fada12, 48a1f83ca9c68518b1a783c62e6a8223144fa9fc, a2fd6dbc98be1105a1d8e9e31575da8873ef115c, a6d2a8b211c874971ee4cf3ddd167408177f6e76, 1d7f1049035b2060342f11eff957cf567d810bdc, f01d6619045704d78613b14e2e0420bfdb7f1c15, aaef73821a3b0194a01bd23ca77774f704a04d40, 5.4.275, 5.10.216, 5.15.157, 5.17 |
| Linux/Linuxgeneric | 5.17 | Not reported |
| linux/linux_kernelgeneric | >=c056a6ba35e0 <68a28f551e46 || >=23e9d815fad8 <48a1f83ca9c6 || >=7a9ad4aceb02 <a2fd6dbc98be || >=6d98eb95b450 <a6d2a8b211c8 || >=6d98eb95b450 <1d7f1049035b || >=6d98eb95b450 <f01d66190457 || >=6d98eb95b450 <aaef73821a3b | 68a28f551e46, 48a1f83ca9c6, a2fd6dbc98be, a6d2a8b211c8, 1d7f1049035b, f01d66190457, aaef73821a3b |
| linux/linux_kernelgeneric | 5.17 | Not reported |
Published upstream
Apr 24, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 5, 2026
In the Linux kernel, the following vulnerability has been resolved: binder: check offset alignment in binder_get_object() Commit 6d98eb95b450 ("binder: avoid potential data leakage when copying txn") introduced changes to how binder objects are copied. In doing so, it unintentionally removed an offset alignment check done through calls to binder_alloc_copy_from_buffer() -> check_buffer(). These calls were replaced in binder_get_object() with copy_from_user(), so now an explicit offset alignment check is needed here. This avoids later complications when unwinding the objects gets harder. It is worth noting this check existed prior to commit 7a67a39320df ("binder: add function to copy binder object from buffer"), likely removed due to redundancy at the time.
Quoted source text, attributed separately from HOL analysis.