linux — security advisory
In the Linux kernel, the following vulnerability has been resolved: jbd2: check 'jh->b_transaction' before removing it from checkpoint Following process will corrupt ext4 image: Step 1: jbd2_journal_commit_transaction __jbd2_journal_insert_checkpoint(jh, commit_transaction) // Put jh into trans1->t_checkpoint_list journal->j_checkpoint_transactions = commit_transaction // Put trans1 into journal->j_checkpoint_transactions Step 2: do_get_write_access test_clear_buffer_dirty(bh) // clear buffer dirty,set jbd dirty __jbd2_journal_file_buffer(jh, transaction) // jh belongs to trans2 Step 3: drop_cache journal_shrink_one_cp_list jbd2_journal_try_remove_checkpoint if (!trylock_buffer(bh)) // lock bh, true if (buffer_dirty(bh)) // buffer is not dirty __jbd2_journal_remove_checkpoint(jh) // remove jh from trans1->t_checkpoint_list Step 4: jbd2_log_do_checkpoint trans1 = journal->j_checkpoint_transactions // jh is not in trans1->t_checkpoint_list jbd2_cleanup_journal_tail(journal) // trans1 is done Step 5: Power cut, trans2 is not committed, jh is lost in next mounting. Fix it by checking 'jh->b_transaction' before remove it from checkpoint.
- 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~bpo11+1
- Fixed versions
- 6.1.55-1, 6.5.6-1
- CVEs
- CVE-2023-53526
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 1 Nov 2026, 16:17 UTC · Revision 1
Source evidence
In the Linux kernel, the following vulnerability has been resolved: jbd2: check 'jh->b_transaction' before removing it from checkpoint Following process will corrupt ext4 image: Step 1: jbd2_journal_commit_transaction __jbd2_journal_insert_checkpoint(jh, commit_transaction) // Put jh into trans1->t_checkpoint_list journal->j_checkpoint_transactions = commit_transaction // Put trans1 into journal->j_checkpoint_transactions Step 2: do_get_write_access test_clear_buffer_dirty(bh) // clear buffer dirty,set jbd dirty __jbd2_journal_file_buffer(jh, transaction) // jh belongs to trans2 Step 3: drop_cache journal_shrink_one_cp_list jbd2_journal_try_remove_checkpoint if (!trylock_buffer(bh)) // lock bh, true if (buffer_dirty(bh)) // buffer is not dirty __jbd2_journal_remove_checkpoint(jh) // remove jh from trans1->t_checkpoint_list Step 4: jbd2_log_do_checkpoint trans1 = journal->j_checkpoint_transactions // jh is not in trans1->t_checkpoint_list jbd2_cleanup_journal_tail(journal) // trans1 is done Step 5: Power cut, trans2 is not committed, jh is lost in next mounting. Fix it by checking 'jh->b_transaction' before remove it from checkpoint.
osv:DEBIAN-CVE-2023-53526
linux
Fixed versions: 6.1.55-1
linux
Fixed versions: 6.5.6-1
linux
Fixed versions: 6.5.6-1
Complete source record
{
"id": "870db2a335e33b589027c2986cfd4e687cfc3fc198b6a56b6973a7ae0e3e81b4",
"url": "https://osv.dev/vulnerability/DEBIAN-CVE-2023-53526",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "DEBIAN-CVE-2023-53526",
"summary": "In the Linux kernel, the following vulnerability has been resolved: jbd2: check 'jh->b_transaction' before removing it from checkpoint Following process will corrupt ext4 image: Step 1: jbd2_journal_commit_transaction __jbd2_journal_insert_checkpoint(jh, commit_transaction) // Put jh into trans1->t_checkpoint_list journal->j_checkpoint_transactions = commit_transaction // Put trans1 into journal->j_checkpoint_transactions Step 2: do_get_write_access test_clear_buffer_dirty(bh) // clear buffer dirty,set jbd dirty __jbd2_journal_file_buffer(jh, transaction) // jh belongs to trans2 Step 3: drop_cache journal_shrink_one_cp_list jbd2_journal_try_remove_checkpoint if (!trylock_buffer(bh)) // lock bh, true if (buffer_dirty(bh)) // buffer is not dirty __jbd2_journal_remove_checkpoint(jh) // remove jh from trans1->t_checkpoint_list Step 4: jbd2_log_do_checkpoint trans1 = journal->j_checkpoint_transactions // jh is not in trans1->t_checkpoint_list jbd2_cleanup_journal_tail(journal) // trans1 is done Step 5: Power cut, trans2 is not committed, jh is lost in next mounting. Fix it by checking 'jh->b_transaction' before remove it from checkpoint.",
"evidence": "osv:DEBIAN-CVE-2023-53526",
"products": [
{
"name": {
"value": "linux",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.1.55-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~bpo11+1",
"evidence": "/affected/0/versions"
}
]
},
{
"name": {
"value": "linux",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.5.6-1",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
},
{
"name": {
"value": "linux",
"evidence": "/affected/2/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.5.6-1",
"evidence": "/affected/2/ranges"
}
],
"affected_versions": []
}
],
"severity": "medium",
"structured": {
"id": "DEBIAN-CVE-2023-53526",
"aliases": [
"DEBIAN-CVE-2023-53526"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
}
],
"affected": [
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "6.1.55-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~bpo11+1"
],
"database_specific": {
"source": "https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2023-53526.json"
},
"ecosystem_specific": {
"urgency": "not yet assigned"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "6.5.6-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-53526.json"
},
"ecosystem_specific": {
"urgency": "not yet assigned"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "6.5.6-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-53526.json"
},
"ecosystem_specific": {
"urgency": "not yet assigned"
}
}
],
"modified": "2026-10-26T18:02:57.707985983Z",
"provider": "osv",
"upstream": [
"CVE-2023-53526"
],
"references": [
"https://security-tracker.debian.org/tracker/CVE-2023-53526"
]
},
"related_cves": [
{
"value": "CVE-2023-53526",
"evidence": "/upstream"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 457266,
"published_at": "2025-10-01T12:15:57.177+00:00"
}