{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-49282 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-49282 is a medium-severity vulnerability in Linux kernel, published on 26 Feb 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-49282 and fix it if it is affected.\n\nWhat it is: CVE-2022-49282 is a medium-severity vulnerability in Linux kernel, published on 26 Feb 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-49282 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-49282/ (Markdown: https://insights.sbomify.com/CVE-2022-49282/index.md)","id":"CVE-2022-49282","markdown":"https://insights.sbomify.com/CVE-2022-49282/index.md","name":"CVE-2022-49282","record":{"aliases":["DEBIAN-CVE-2022-49282","GHSA-fc4w-ww8r-wx6x","UBUNTU-CVE-2022-49282"],"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 logic error in the Linux kernel's f2fs quota synchronization can lead to a NULL pointer dereference, causing a system crash.","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":"cisa-adp","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\nf2fs: quota: fix loop condition at f2fs_quota_sync()\n\ncnt should be passed to sb_has_quota_active() instead of type to check\nactive quota properly.\n\nMoreover, when the type is -1, the compiler with enough inline knowledge\ncan discard sb_has_quota_active() check altogether, causing a NULL pointer\ndereference at the following inode_lock(dqopt-\u003efiles[cnt]):\n\n[    2.796010] Unable to handle kernel NULL pointer dereference at virtual address 00000000000000a0\n[    2.796024] Mem abort info:\n[    2.796025]   ESR = 0x96000005\n[    2.796028]   EC = 0x25: DABT (current EL), IL = 32 bits\n[    2.796029]   SET = 0, FnV = 0\n[    2.796031]   EA = 0, S1PTW = 0\n[    2.796032] Data abort info:\n[    2.796034]   ISV = 0, ISS = 0x00000005\n[    2.796035]   CM = 0, WnR = 0\n[    2.796046] user pgtable: 4k pages, 39-bit VAs, pgdp=00000003370d1000\n[    2.796048] [00000000000000a0] pgd=0000000000000000, pud=0000000000000000\n[    2.796051] Internal error: Oops: 96000005 [#1] PREEMPT SMP\n[    2.796056] CPU: 7 PID: 640 Comm: f2fs_ckpt-259:7 Tainted: G S                5.4.179-arter97-r8-64666-g2f16e087f9d8 #1\n[    2.796057] Hardware name: Qualcomm Technologies, Inc. Lahaina MTP lemonadep (DT)\n[    2.796059] pstate: 80c00005 (Nzcv daif +PAN +UAO)\n[    2.796065] pc : down_write+0x28/0x70\n[    2.796070] lr : f2fs_quota_sync+0x100/0x294\n[    2.796071] sp : ffffffa3f48ffc30\n[    2.796073] x29: ffffffa3f48ffc30 x28: 0000000000000000\n[    2.796075] x27: ffffffa3f6d718b8 x26: ffffffa415fe9d80\n[    2.796077] x25: ffffffa3f7290048 x24: 0000000000000001\n[    2.796078] x23: 0000000000000000 x22: ffffffa3f7290000\n[    2.796080] x21: ffffffa3f72904a0 x20: ffffffa3f7290110\n[    2.796081] x19: ffffffa3f77a9800 x18: ffffffc020aae038\n[    2.796083] x17: ffffffa40e38e040 x16: ffffffa40e38e6d0\n[    2.796085] x15: ffffffa40e38e6cc x14: ffffffa40e38e6d0\n[    2.796086] x13: 00000000000004f6 x12: 00162c44ff493000\n[    2.796088] x11: 0000000000000400 x10: ffffffa40e38c948\n[    2.796090] x9 : 0000000000000000 x8 : 00000000000000a0\n[    2.796091] x7 : 0000000000000000 x6 : 0000d1060f00002a\n[    2.796093] x5 : ffffffa3f48ff718 x4 : 000000000000000d\n[    2.796094] x3 : 00000000060c0000 x2 : 0000000000000001\n[    2.796096] x1 : 0000000000000000 x0 : 00000000000000a0\n[    2.796098] Call trace:\n[    2.796100]  down_write+0x28/0x70\n[    2.796102]  f2fs_quota_sync+0x100/0x294\n[    2.796104]  block_operations+0x120/0x204\n[    2.796106]  f2fs_write_checkpoint+0x11c/0x520\n[    2.796107]  __checkpoint_and_complete_reqs+0x7c/0xd34\n[    2.796109]  issue_checkpoint_thread+0x6c/0xb8\n[    2.796112]  kthread+0x138/0x414\n[    2.796114]  ret_from_fork+0x10/0x18\n[    2.796117] Code: aa0803e0 aa1f03e1 52800022 aa0103e9 (c8e97d02)\n[    2.796120] ---[ end trace 96e942e8eb6a0b53 ]---\n[    2.800116] Kernel panic - not syncing: Fatal exception\n[    2.800120] SMP: stopping secondary CPUs","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":"f2fs: quota: fix loop condition at f2fs_quota_sync()","id":"CVE-2022-49282","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":6,"next":{"headline":"firmware: sysfb: fix platform-device leak in error path","id":"CVE-2022-49283"},"packages":[],"prev":{"headline":"cifs: fix handlecache and multiuser","id":"CVE-2022-49281"},"products":["Linux"],"published":"2025-02-26","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-23","vendors":["Linux"]},"summary":"A logic error in the Linux kernel's f2fs quota synchronization can lead to a NULL pointer dereference, causing a system crash.","url":"https://insights.sbomify.com/CVE-2022-49282/"}