SECUFOCUSNOW
Home›CVE index›CVE-2023-53616
Review reviewHigh

CVE-2023-53616

Linux Linux, linux kernel

In the Linux kernel, the following vulnerability has been resolved: jfs: fix invalid free of JFS_IP(ipimap)->i_imap in diUnmount syzbot found an invalid-free in diUnmount: BUG: KASAN: double-free in slab_free mm/slub.c:3661 [inline] BUG: KASAN: double-free in __kmem_cache_free+0x71/0x110 mm/slub.c:3674 Free of addr ffff88806f410000 by task syz-executor131/3632 CPU: 0 PID: 3632 Comm: syz-executor131 Not tainted 6.1.0-rc7-syzkaller-00012-gca57f02295f1 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 Call Trace: <TASK> __dump_stack lib/dump_stack.c:8...

CVSS
7.8
EPSS
0.14%
4.05% percentile
CISA KEV
Not listed
Published
2025.10.05
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability0.14%
Technical severityCVSS 7.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: jfs: fix invalid free of JFS_IP(ipimap)->i_imap in diUnmount syzbot found an invalid-free in diUnmount: BUG: KASAN: double-free in slab_free mm/slub.c:3661 [inline] BUG: KASAN: double-free in __kmem_cache_free+0x71/0x110 mm/slub.c:3674 Free of addr ffff88806f410000 by task syz-executor131/3632 CPU: 0 PID: 3632 Comm: syz-executor131 Not tainted 6.1.0-rc7-syzkaller-00012-gca57f02295f1 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022 Call Trace: <TASK> __dump_stack lib/dump_stack.c:8...

Affected product and versions

Product
Linux Linux, linux kernel
Affected versions
>= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < c3c0f0ddd851b3fa3e9d3450bbcd561f4f850469, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 114ea3cb13ab25f7178cb60283adb93d2f96dad7, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 5873df0195124be2f357de11bfd473ead4f90ed8, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 756747d4b439e3e1159282ae89f17eefebbe9b25, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < ef7311101ca43dd73b45bca7a30ac72d9535ff87, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 4de3a603010e0ca334487de24c6aab0777b7f808, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 88484bde6f12126616b38e43b6c00edcd941f615, >= 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 < 6e2bda2c192d0244b5a78b787ef20aa10cb319b7, >= 2.6.12, >= 2.6.12.1 < 4.14.326, >= 4.15 < 4.19.295, >= 4.20 < 5.4.257, >= 5.5 < 5.10.197, >= 5.11 < 5.15.133, >= 5.16 < 6.1.55, >= 6.2 < 6.5.5, 2.6.12
Fixed versions
4.14.326, 4.19.295, 5.4.257, 5.10.197, 5.15.133, 6.1.55, 6.5.5

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux Linux, linux kernel and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
CWE-415