Answer in brief
CVE-2026-53049 records a Critical severity (CVSS 9.8) vulnerability in gfs2: add some missing log locking. 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 9.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 | >=5e4c7632aae1cce137792647f4fb6f599d1da893 <3b28eb75afe520972bacc833850c2b30aa0824cd || >=5e4c7632aae1cce137792647f4fb6f599d1da893 <ca95342cb1b39062a03c115830286f0a426053d5 || >=5e4c7632aae1cce137792647f4fb6f599d1da893 <bf5fcd9c37c2546beaf7b401d31aefd89017dc3d || >=5e4c7632aae1cce137792647f4fb6f599d1da893 <f2f225cf505ac016132ded21690f3ba0a080a4e8 || >=5e4c7632aae1cce137792647f4fb6f599d1da893 <49d9be0722da3a4a893ba905720cba1921834ec3 || >=5e4c7632aae1cce137792647f4fb6f599d1da893 <98e8bf249c790d56de1abc4a5f8bd68035a00921 || >=5e4c7632aae1cce137792647f4fb6f599d1da893 <fe2c8d051150b90b3ccb85f89e3b1d636cb88ec8 | 3b28eb75afe520972bacc833850c2b30aa0824cd, ca95342cb1b39062a03c115830286f0a426053d5, bf5fcd9c37c2546beaf7b401d31aefd89017dc3d, f2f225cf505ac016132ded21690f3ba0a080a4e8, 49d9be0722da3a4a893ba905720cba1921834ec3, 98e8bf249c790d56de1abc4a5f8bd68035a00921, fe2c8d051150b90b3ccb85f89e3b1d636cb88ec8 |
| Linux/Linuxgeneric | 5.7 | Not reported |
Published upstream
Jun 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 24, 2026
In the Linux kernel, the following vulnerability has been resolved: gfs2: add some missing log locking Function gfs2_logd() calls the log flushing functions gfs2_ail1_start(), gfs2_ail1_wait(), and gfs2_ail1_empty() without holding sdp->sd_log_flush_lock, but these functions require exclusion against concurrent transactions. To fix that, add a non-locking __gfs2_log_flush() function. Then, in gfs2_logd(), take sdp->sd_log_flush_lock before calling the above mentioned log flushing functions and __gfs2_log_flush().
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2026-53049 records a Critical severity (CVSS 9.8) vulnerability in gfs2: add some missing log locking. 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 9.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 | >=5e4c7632aae1cce137792647f4fb6f599d1da893 <3b28eb75afe520972bacc833850c2b30aa0824cd || >=5e4c7632aae1cce137792647f4fb6f599d1da893 <ca95342cb1b39062a03c115830286f0a426053d5 || >=5e4c7632aae1cce137792647f4fb6f599d1da893 <bf5fcd9c37c2546beaf7b401d31aefd89017dc3d || >=5e4c7632aae1cce137792647f4fb6f599d1da893 <f2f225cf505ac016132ded21690f3ba0a080a4e8 || >=5e4c7632aae1cce137792647f4fb6f599d1da893 <49d9be0722da3a4a893ba905720cba1921834ec3 || >=5e4c7632aae1cce137792647f4fb6f599d1da893 <98e8bf249c790d56de1abc4a5f8bd68035a00921 || >=5e4c7632aae1cce137792647f4fb6f599d1da893 <fe2c8d051150b90b3ccb85f89e3b1d636cb88ec8 | 3b28eb75afe520972bacc833850c2b30aa0824cd, ca95342cb1b39062a03c115830286f0a426053d5, bf5fcd9c37c2546beaf7b401d31aefd89017dc3d, f2f225cf505ac016132ded21690f3ba0a080a4e8, 49d9be0722da3a4a893ba905720cba1921834ec3, 98e8bf249c790d56de1abc4a5f8bd68035a00921, fe2c8d051150b90b3ccb85f89e3b1d636cb88ec8 |
| Linux/Linuxgeneric | 5.7 | Not reported |
Published upstream
Jun 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 5, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 24, 2026
In the Linux kernel, the following vulnerability has been resolved: gfs2: add some missing log locking Function gfs2_logd() calls the log flushing functions gfs2_ail1_start(), gfs2_ail1_wait(), and gfs2_ail1_empty() without holding sdp->sd_log_flush_lock, but these functions require exclusion against concurrent transactions. To fix that, add a non-locking __gfs2_log_flush() function. Then, in gfs2_logd(), take sdp->sd_log_flush_lock before calling the above mentioned log flushing functions and __gfs2_log_flush().
Quoted source text, attributed separately from HOL analysis.