{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-50262 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-50262 is a medium-severity vulnerability in Linux kernel, published on 15 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-50262 and fix it if it is affected.\n\nWhat it is: CVE-2022-50262 is a medium-severity vulnerability in Linux kernel, published on 15 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-50262 in the wild and no public exploit code.\n\nAffected product: Linux kernel. 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-50262/ (Markdown: https://insights.sbomify.com/CVE-2022-50262/index.md)","id":"CVE-2022-50262","markdown":"https://insights.sbomify.com/CVE-2022-50262/index.md","name":"CVE-2022-50262","record":{"aliases":["DEBIAN-CVE-2022-50262","GHSA-mprr-p5pf-vhc3","UBUNTU-CVE-2022-50262"],"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 malformed NTFS image due to missing validation of the BOOT record size.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-476","name":"NULL Pointer Dereference"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nfs/ntfs3: Validate BOOT record_size\n\nWhen the NTFS BOOT record_size field \u003c 0, it represents a\nshift value. However, there is no sanity check on the shift result\nand the sbi-\u003erecord_bits calculation through blksize_bits() assumes\nthe size always \u003e 256, which could lead to NPD while mounting a\nmalformed NTFS image.\n\n[  318.675159] BUG: kernel NULL pointer dereference, address: 0000000000000158\n[  318.675682] #PF: supervisor read access in kernel mode\n[  318.675869] #PF: error_code(0x0000) - not-present page\n[  318.676246] PGD 0 P4D 0\n[  318.676502] Oops: 0000 [#1] PREEMPT SMP NOPTI\n[  318.676934] CPU: 0 PID: 259 Comm: mount Not tainted 5.19.0 #5\n[  318.677289] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.14.0-0-g155821a1990b-prebuilt.qemu.org 04/01/2014\n[  318.678136] RIP: 0010:ni_find_attr+0x2d/0x1c0\n[  318.678656] Code: 89 ca 4d 89 c7 41 56 41 55 41 54 41 89 cc 55 48 89 fd 53 48 89 d3 48 83 ec 20 65 48 8b 04 25 28 00 00 00 48 89 44 24 180\n[  318.679848] RSP: 0018:ffffa6c8c0297bd8 EFLAGS: 00000246\n[  318.680104] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000080\n[  318.680790] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000\n[  318.681679] RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000\n[  318.682577] R10: 0000000000000000 R11: 0000000000000005 R12: 0000000000000080\n[  318.683015] R13: ffff8d5582e68400 R14: 0000000000000100 R15: 0000000000000000\n[  318.683618] FS:  00007fd9e1c81e40(0000) GS:ffff8d55fdc00000(0000) knlGS:0000000000000000\n[  318.684280] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033\n[  318.684651] CR2: 0000000000000158 CR3: 0000000002e1a000 CR4: 00000000000006f0\n[  318.685623] Call Trace:\n[  318.686607]  \u003cTASK\u003e\n[  318.686872]  ? ntfs_alloc_inode+0x1a/0x60\n[  318.687235]  attr_load_runs_vcn+0x2b/0xa0\n[  318.687468]  mi_read+0xbb/0x250\n[  318.687576]  ntfs_iget5+0x114/0xd90\n[  318.687750]  ntfs_fill_super+0x588/0x11b0\n[  318.687953]  ? put_ntfs+0x130/0x130\n[  318.688065]  ? snprintf+0x49/0x70\n[  318.688164]  ? put_ntfs+0x130/0x130\n[  318.688256]  get_tree_bdev+0x16a/0x260\n[  318.688407]  vfs_get_tree+0x20/0xb0\n[  318.688519]  path_mount+0x2dc/0x9b0\n[  318.688877]  do_mount+0x74/0x90\n[  318.689142]  __x64_sys_mount+0x89/0xd0\n[  318.689636]  do_syscall_64+0x3b/0x90\n[  318.689998]  entry_SYSCALL_64_after_hwframe+0x63/0xcd\n[  318.690318] RIP: 0033:0x7fd9e133c48a\n[  318.690687] 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[  318.691357] RSP: 002b:00007ffd374406c8 EFLAGS: 00000202 ORIG_RAX: 00000000000000a5\n[  318.691632] RAX: ffffffffffffffda RBX: 0000564d0b051080 RCX: 00007fd9e133c48a\n[  318.691920] RDX: 0000564d0b051280 RSI: 0000564d0b051300 RDI: 0000564d0b0596a0\n[  318.692123] RBP: 0000000000000000 R08: 0000564d0b0512a0 R09: 0000000000000020\n[  318.692349] R10: 00000000c0ed0000 R11: 0000000000000202 R12: 0000564d0b0596a0\n[  318.692673] R13: 0000564d0b051280 R14: 0000000000000000 R15: 00000000ffffffff\n[  318.693007]  \u003c/TASK\u003e\n[  318.693271] Modules linked in:\n[  318.693614] CR2: 0000000000000158\n[  318.694446] ---[ end trace 0000000000000000 ]---\n[  318.694779] RIP: 0010:ni_find_attr+0x2d/0x1c0\n[  318.694952] Code: 89 ca 4d 89 c7 41 56 41 55 41 54 41 89 cc 55 48 89 fd 53 48 89 d3 48 83 ec 20 65 48 8b 04 25 28 00 00 00 48 89 44 24 180\n[  318.696042] RSP: 0018:ffffa6c8c0297bd8 EFLAGS: 00000246\n[  318.696531] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000080\n[  318.698114] RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000\n[  318.699286] RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000\n[  318.699795] R10: 0000000000000000 R11: 0000000000000005 R12: 0000000000000080\n[  318.700236] R13: ffff8d5582e68400 R14: 0000000000000100 R15: 0000000000000000\n[  318.700973] FS:  00007fd9e1c81e40(0000) GS:ffff8d55fdc00000(0000) knlGS:0000000000000000\n[\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: Validate BOOT record_size","id":"CVE-2022-50262","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"null_dereference","year":"2022"},"n_packages":0,"n_references":4,"next":{"headline":"vdpasim: fix memory leak when freeing IOTLBs","id":"CVE-2022-50263"},"packages":[],"prev":{"headline":"drm/sti: Fix return type of sti_{dvo,hda,hdmi}_connector_mode_valid()","id":"CVE-2022-50261"},"products":["Linux"],"published":"2025-09-15","related":[{"cvss_score":8.8,"headline":"Linux Kernel Out-of-Bounds Write","id":"CVE-2026-53266","kev_date_added":"2026-09-18","published":"2026-06-25"},{"cvss_score":8.8,"headline":"Linux Kernel Improper Input Validation","id":"CVE-2013-6282","kev_date_added":"2022-09-15","published":"2013-11-19"},{"cvss_score":8.4,"headline":"Linux Kernel Heap-Based Buffer Overflow","id":"CVE-2022-0185","kev_date_added":"2024-08-21","published":"2022-02-11"},{"cvss_score":8.4,"headline":"Linux Kernel Privilege Escalation","id":"CVE-2013-2094","kev_date_added":"2022-09-15","published":"2013-05-14"},{"cvss_score":7.8,"headline":"Linux Kernel Unspecified","id":"CVE-2026-53362","kev_date_added":"2026-08-27","published":"2026-07-04"},{"cvss_score":7.8,"headline":"Linux Kernel Missing Initialization of a Variable","id":"CVE-2026-46300","kev_date_added":"2026-10-28","published":"2026-05-23"},{"cvss_score":7.8,"headline":"Linux Kernel Race Condition","id":"CVE-2025-39964","kev_date_added":"2026-09-18","published":"2025-10-13"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-15","vendors":["Linux"]},"summary":"A local attacker can cause a kernel crash by mounting a malformed NTFS image due to missing validation of the BOOT record size.","url":"https://insights.sbomify.com/CVE-2022-50262/"}