{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2022-50724 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-50724 is a memory corruption vulnerability in Linux, published on 24 Dec 2025."},"fix_prompt":"Check this codebase for CVE-2022-50724 and fix it if it is affected.\n\nWhat it is: CVE-2022-50724 is a memory corruption vulnerability in Linux, published on 24 Dec 2025. \nExploitation: There is no known exploitation of CVE-2022-50724 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-50724/ (Markdown: https://insights.sbomify.com/CVE-2022-50724/index.md)","id":"CVE-2022-50724","markdown":"https://insights.sbomify.com/CVE-2022-50724/index.md","name":"CVE-2022-50724","record":{"aliases":["DEBIAN-CVE-2022-50724","GHSA-wr64-83w3-wr39","UBUNTU-CVE-2022-50724"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"unknown","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A resource leak in the Linux kernel regulator core can lead to memory exhaustion and denial of service during device registration failures.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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\nregulator: core: fix resource leak in regulator_register()\n\nI got some resource leak reports while doing fault injection test:\n\n  OF: ERROR: memory leak, expected refcount 1 instead of 100,\n  of_node_get()/of_node_put() unbalanced - destroy cset entry:\n  attach overlay node /i2c/pmic@64/regulators/buck1\n\nunreferenced object 0xffff88810deea000 (size 512):\n  comm \"490-i2c-rt5190a\", pid 253, jiffies 4294859840 (age 5061.046s)\n  hex dump (first 32 bytes):\n    00 00 00 00 ad 4e ad de ff ff ff ff 00 00 00 00  .....N..........\n    ff ff ff ff ff ff ff ff a0 1e 00 a1 ff ff ff ff  ................\n  backtrace:\n    [\u003c00000000d78541e2\u003e] kmalloc_trace+0x21/0x110\n    [\u003c00000000b343d153\u003e] device_private_init+0x32/0xd0\n    [\u003c00000000be1f0c70\u003e] device_add+0xb2d/0x1030\n    [\u003c00000000e3e6344d\u003e] regulator_register+0xaf2/0x12a0\n    [\u003c00000000e2f5e754\u003e] devm_regulator_register+0x57/0xb0\n    [\u003c000000008b898197\u003e] rt5190a_probe+0x52a/0x861 [rt5190a_regulator]\n\nunreferenced object 0xffff88810b617b80 (size 32):\n  comm \"490-i2c-rt5190a\", pid 253, jiffies 4294859904 (age 5060.983s)\n  hex dump (first 32 bytes):\n    72 65 67 75 6c 61 74 6f 72 2e 32 38 36 38 2d 53  regulator.2868-S\n    55 50 50 4c 59 00 ff ff 29 00 00 00 2b 00 00 00  UPPLY...)...+...\n  backtrace:\n    [\u003c000000009da9280d\u003e] __kmalloc_node_track_caller+0x44/0x1b0\n    [\u003c0000000025c6a4e5\u003e] kstrdup+0x3a/0x70\n    [\u003c00000000790efb69\u003e] create_regulator+0xc0/0x4e0\n    [\u003c0000000005ed203a\u003e] regulator_resolve_supply+0x2d4/0x440\n    [\u003c0000000045796214\u003e] regulator_register+0x10b3/0x12a0\n    [\u003c00000000e2f5e754\u003e] devm_regulator_register+0x57/0xb0\n    [\u003c000000008b898197\u003e] rt5190a_probe+0x52a/0x861 [rt5190a_regulator]\n\nAfter calling regulator_resolve_supply(), the 'rdev-\u003esupply' is set\nby set_supply(), after this set, in the error path, the resources\nneed be released, so call regulator_put() to avoid the leaks.","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":"regulator: core: fix resource leak in regulator_register()","id":"CVE-2022-50724","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2022"},"n_packages":0,"n_references":6,"next":{"headline":"media: vidtv: Fix use-after-free in vidtv_bridge_dvb_init()","id":"CVE-2022-50725"},"packages":[],"prev":{"headline":"bnxt_en: fix memory leak in bnxt_nvm_test()","id":"CVE-2022-50723"},"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-23","vendors":["Linux"]},"summary":"A resource leak in the Linux kernel regulator core can lead to memory exhaustion and denial of service during device registration failures.","url":"https://insights.sbomify.com/CVE-2022-50724/"}