{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-49706 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-49706 is a high-severity denial of service 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-49706 and fix it if it is affected.\n\nWhat it is: CVE-2022-49706 is a high-severity denial of service 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-49706 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-49706/ (Markdown: https://insights.sbomify.com/CVE-2022-49706/index.md)","id":"CVE-2022-49706","markdown":"https://insights.sbomify.com/CVE-2022-49706/index.md","name":"CVE-2022-49706","record":{"aliases":["DEBIAN-CVE-2022-49706","GHSA-fv86-c5hh-rvpj","UBUNTU-CVE-2022-49706"],"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 trigger a kernel warning and infinite loop in the zonefs filesystem by reading a sequential zone file at a specific offset, causing a denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[{"product":"linux_kernel","vendor":"linux"}],"cvss":{"score":7.1,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nzonefs: fix zonefs_iomap_begin() for reads\n\nIf a readahead is issued to a sequential zone file with an offset\nexactly equal to the current file size, the iomap type is set to\nIOMAP_UNWRITTEN, which will prevent an IO, but the iomap length is\ncalculated as 0. This causes a WARN_ON() in iomap_iter():\n\n[17309.548939] WARNING: CPU: 3 PID: 2137 at fs/iomap/iter.c:34 iomap_iter+0x9cf/0xe80\n[...]\n[17309.650907] RIP: 0010:iomap_iter+0x9cf/0xe80\n[...]\n[17309.754560] Call Trace:\n[17309.757078]  \u003cTASK\u003e\n[17309.759240]  ? lock_is_held_type+0xd8/0x130\n[17309.763531]  iomap_readahead+0x1a8/0x870\n[17309.767550]  ? iomap_read_folio+0x4c0/0x4c0\n[17309.771817]  ? lockdep_hardirqs_on_prepare+0x400/0x400\n[17309.778848]  ? lock_release+0x370/0x750\n[17309.784462]  ? folio_add_lru+0x217/0x3f0\n[17309.790220]  ? reacquire_held_locks+0x4e0/0x4e0\n[17309.796543]  read_pages+0x17d/0xb60\n[17309.801854]  ? folio_add_lru+0x238/0x3f0\n[17309.807573]  ? readahead_expand+0x5f0/0x5f0\n[17309.813554]  ? policy_node+0xb5/0x140\n[17309.819018]  page_cache_ra_unbounded+0x27d/0x450\n[17309.825439]  filemap_get_pages+0x500/0x1450\n[17309.831444]  ? filemap_add_folio+0x140/0x140\n[17309.837519]  ? lock_is_held_type+0xd8/0x130\n[17309.843509]  filemap_read+0x28c/0x9f0\n[17309.848953]  ? zonefs_file_read_iter+0x1ea/0x4d0 [zonefs]\n[17309.856162]  ? trace_contention_end+0xd6/0x130\n[17309.862416]  ? __mutex_lock+0x221/0x1480\n[17309.868151]  ? zonefs_file_read_iter+0x166/0x4d0 [zonefs]\n[17309.875364]  ? filemap_get_pages+0x1450/0x1450\n[17309.881647]  ? __mutex_unlock_slowpath+0x15e/0x620\n[17309.888248]  ? wait_for_completion_io_timeout+0x20/0x20\n[17309.895231]  ? lock_is_held_type+0xd8/0x130\n[17309.901115]  ? lock_is_held_type+0xd8/0x130\n[17309.906934]  zonefs_file_read_iter+0x356/0x4d0 [zonefs]\n[17309.913750]  new_sync_read+0x2d8/0x520\n[17309.919035]  ? __x64_sys_lseek+0x1d0/0x1d0\n\nFurthermore, this causes iomap_readahead() to loop forever as\niomap_readahead_iter() always returns 0, making no progress.\n\nFix this by treating reads after the file size as access to holes,\nsetting the iomap type to IOMAP_HOLE, the iomap addr to IOMAP_NULL_ADDR\nand using the length argument as is for the iomap length. To simplify\nthe code with this change, zonefs_iomap_begin() is split into the read\nvariant, zonefs_read_iomap_begin() and zonefs_read_iomap_ops, and the\nwrite variant, zonefs_write_iomap_begin() and zonefs_write_iomap_ops.","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":"zonefs: fix zonefs_iomap_begin() for reads","id":"CVE-2022-49706","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"denial_of_service","year":"2022"},"n_packages":0,"n_references":4,"next":{"headline":"ext4: add reserved GDT blocks check","id":"CVE-2022-49707"},"packages":[],"prev":{"headline":"9p: fix fid refcount leak in v9fs_vfs_atomic_open_dotl","id":"CVE-2022-49705"},"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-05-11","vendors":["Linux"]},"summary":"A local attacker can trigger a kernel warning and infinite loop in the zonefs filesystem by reading a sequential zone file at a specific offset, causing a denial of service.","url":"https://insights.sbomify.com/CVE-2022-49706/"}