{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2022-50739 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-50739 is a vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-50739 and fix it if it is affected.\n\nWhat it is: CVE-2022-50739 is a vulnerability in Linux, published on 24 Dec 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-50739 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-50739/ (Markdown: https://insights.sbomify.com/CVE-2022-50739/index.md)","id":"CVE-2022-50739","markdown":"https://insights.sbomify.com/CVE-2022-50739/index.md","name":"CVE-2022-50739","record":{"aliases":["DEBIAN-CVE-2022-50739","GHSA-9h8x-5g7f-6f2f","UBUNTU-CVE-2022-50739"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"A local attacker can cause a kernel crash by mounting a specially crafted NTFS image, leading to denial of service.","user_interaction":"required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nfs/ntfs3: Add null pointer check for inode operations\n\nThis adds a sanity check for the i_op pointer of the inode which is\nreturned after reading Root directory MFT record. We should check the\ni_op is valid before trying to create the root dentry, otherwise we may\nencounter a NPD while mounting a image with a funny Root directory MFT\nrecord.\n\n[  114.484325] BUG: kernel NULL pointer dereference, address: 0000000000000008\n[  114.484811] #PF: supervisor read access in kernel mode\n[  114.485084] #PF: error_code(0x0000) - not-present page\n[  114.485606] PGD 0 P4D 0\n[  114.485975] Oops: 0000 [#1] PREEMPT SMP KASAN NOPTI\n[  114.486570] CPU: 0 PID: 237 Comm: mount Tainted: G    B              6.0.0-rc4 #28\n[  114.486977] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014\n[  114.488169] RIP: 0010:d_flags_for_inode+0xe0/0x110\n[  114.488816] Code: 24 f7 ff 49 83 3e 00 74 41 41 83 cd 02 66 44 89 6b 02 eb 92 48 8d 7b 20 e8 6d 24 f7 ff 4c 8b 73 20 49 8d 7e 08 e8 60 241\n[  114.490326] RSP: 0018:ffff8880065e7aa8 EFLAGS: 00000296\n[  114.490695] RAX: 0000000000000001 RBX: ffff888008ccd750 RCX: ffffffff84af2aea\n[  114.490986] RDX: 0000000000000001 RSI: 0000000000000008 RDI: ffffffff87abd020\n[  114.491364] RBP: ffff8880065e7ac8 R08: 0000000000000001 R09: fffffbfff0f57a05\n[  114.491675] R10: ffffffff87abd027 R11: fffffbfff0f57a04 R12: 0000000000000000\n[  114.491954] R13: 0000000000000008 R14: 0000000000000000 R15: ffff888008ccd750\n[  114.492397] FS:  00007fdc8a627e40(0000) GS:ffff888058200000(0000) knlGS:0000000000000000\n[  114.492797] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[  114.493150] CR2: 0000000000000008 CR3: 00000000013ba000 CR4: 00000000000006f0\n[  114.493671] Call Trace:\n[  114.493890]  \u003cTASK\u003e\n[  114.494075]  __d_instantiate+0x24/0x1c0\n[  114.494505]  d_instantiate.part.0+0x35/0x50\n[  114.494754]  d_make_root+0x53/0x80\n[  114.494998]  ntfs_fill_super+0x1232/0x1b50\n[  114.495260]  ? put_ntfs+0x1d0/0x1d0\n[  114.495499]  ? vsprintf+0x20/0x20\n[  114.495723]  ? set_blocksize+0x95/0x150\n[  114.495964]  get_tree_bdev+0x232/0x370\n[  114.496272]  ? put_ntfs+0x1d0/0x1d0\n[  114.496502]  ntfs_fs_get_tree+0x15/0x20\n[  114.496859]  vfs_get_tree+0x4c/0x130\n[  114.497099]  path_mount+0x654/0xfe0\n[  114.497507]  ? putname+0x80/0xa0\n[  114.497933]  ? finish_automount+0x2e0/0x2e0\n[  114.498362]  ? putname+0x80/0xa0\n[  114.498571]  ? kmem_cache_free+0x1c4/0x440\n[  114.498819]  ? putname+0x80/0xa0\n[  114.499069]  do_mount+0xd6/0xf0\n[  114.499343]  ? path_mount+0xfe0/0xfe0\n[  114.499683]  ? __kasan_check_write+0x14/0x20\n[  114.500133]  __x64_sys_mount+0xca/0x110\n[  114.500592]  do_syscall_64+0x3b/0x90\n[  114.500930]  entry_SYSCALL_64_after_hwframe+0x63/0xcd\n[  114.501294] RIP: 0033:0x7fdc898e948a\n[  114.501542] Code: 48 8b 0d 11 fa 2a 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 49 89 ca b8 a5 00 00 008\n[  114.502716] RSP: 002b:00007ffd793e58f8 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5\n[  114.503175] RAX: ffffffffffffffda RBX: 0000564b2228f060 RCX: 00007fdc898e948a\n[  114.503588] RDX: 0000564b2228f260 RSI: 0000564b2228f2e0 RDI: 0000564b22297ce0\n[  114.504925] RBP: 0000000000000000 R08: 0000564b2228f280 R09: 0000000000000020\n[  114.505484] R10: 00000000c0ed0000 R11: 0000000000000202 R12: 0000564b22297ce0\n[  114.505823] R13: 0000564b2228f260 R14: 0000000000000000 R15: 00000000ffffffff\n[  114.506562]  \u003c/TASK\u003e\n[  114.506887] Modules linked in:\n[  114.507648] CR2: 0000000000000008\n[  114.508884] ---[ end trace 0000000000000000 ]---\n[  114.509675] RIP: 0010:d_flags_for_inode+0xe0/0x110\n[  114.510140] Code: 24 f7 ff 49 83 3e 00 74 41 41 83 cd 02 66 44 89 6b 02 eb 92 48 8d 7b 20 e8 6d 24 f7 ff 4c 8b 73 20 49 8d 7e 08 e8 60 241\n[  114.511762] RSP: 0018:ffff8880065e7aa8 EFLAGS: 00000296\n[  114.512401] RAX: 0000000000000001 RBX: ffff888008ccd750 RCX: ffffffff84af2aea\n[  114.51\n---truncated---","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"fs/ntfs3: Add null pointer check for inode operations","id":"CVE-2022-50739","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2022"},"n_packages":0,"n_references":4,"next":{"headline":"wifi: ath9k: hif_usb: fix memory leak of urbs in ath9k_hif_usb_dealloc_tx_urbs()","id":"CVE-2022-50740"},"packages":[],"prev":{"headline":"vhost-vdpa: fix an iotlb memory leak","id":"CVE-2022-50738"},"products":["Linux"],"published":"2025-12-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A local attacker can cause a kernel crash by mounting a specially crafted NTFS image, leading to denial of service.","url":"https://insights.sbomify.com/CVE-2022-50739/"}