{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-50477 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2022-50477 is a medium-severity memory corruption vulnerability in Linux kernel, published on 4 Oct 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-50477 and fix it if it is affected.\n\nWhat it is: CVE-2022-50477 is a medium-severity memory corruption vulnerability in Linux kernel, published on 4 Oct 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-50477 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-50477/ (Markdown: https://insights.sbomify.com/CVE-2022-50477/index.md)","id":"CVE-2022-50477","markdown":"https://insights.sbomify.com/CVE-2022-50477/index.md","name":"CVE-2022-50477","record":{"aliases":["DEBIAN-CVE-2022-50477","GHSA-wq62-9p2f-cfr9","UBUNTU-CVE-2022-50477"],"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 memory leak in the Linux kernel RTC driver can lead to resource exhaustion and denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"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-401","name":"Missing Release of Memory after Effective Lifetime"}],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nrtc: class: Fix potential memleak in devm_rtc_allocate_device()\n\ndevm_rtc_allocate_device() will alloc a rtc_device first, and then run\ndev_set_name(). If dev_set_name() failed, the rtc_device will memleak.\nMove devm_add_action_or_reset() in front of dev_set_name() to prevent\nmemleak.\n\nunreferenced object 0xffff888110a53000 (size 2048):\n  comm \"python3\", pid 470, jiffies 4296078308 (age 58.882s)\n  hex dump (first 32 bytes):\n    00 00 00 00 00 00 00 00 08 30 a5 10 81 88 ff ff  .........0......\n    08 30 a5 10 81 88 ff ff 00 00 00 00 00 00 00 00  .0..............\n  backtrace:\n    [\u003c000000004aac0364\u003e] kmalloc_trace+0x21/0x110\n    [\u003c000000000ff02202\u003e] devm_rtc_allocate_device+0xd4/0x400\n    [\u003c000000001bdf5639\u003e] devm_rtc_device_register+0x1a/0x80\n    [\u003c00000000351bf81c\u003e] rx4581_probe+0xdd/0x110 [rtc_rx4581]\n    [\u003c00000000f0eba0ae\u003e] spi_probe+0xde/0x130\n    [\u003c00000000bff89ee8\u003e] really_probe+0x175/0x3f0\n    [\u003c00000000128e8d84\u003e] __driver_probe_device+0xe6/0x170\n    [\u003c00000000ee5bf913\u003e] device_driver_attach+0x32/0x80\n    [\u003c00000000f3f28f92\u003e] bind_store+0x10b/0x1a0\n    [\u003c000000009ff812d8\u003e] drv_attr_store+0x49/0x70\n    [\u003c000000008139c323\u003e] sysfs_kf_write+0x8d/0xb0\n    [\u003c00000000b6146e01\u003e] kernfs_fop_write_iter+0x214/0x2d0\n    [\u003c00000000ecbe3895\u003e] vfs_write+0x61a/0x7d0\n    [\u003c00000000aa2196ea\u003e] ksys_write+0xc8/0x190\n    [\u003c0000000046a600f5\u003e] do_syscall_64+0x37/0x90\n    [\u003c00000000541a336f\u003e] entry_SYSCALL_64_after_hwframe+0x63/0xcd","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":"rtc: class: Fix potential memleak in devm_rtc_allocate_device()","id":"CVE-2022-50477","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"linux:linux_kernel","products":["linux:linux_kernel"],"type":"memory_corruption","year":"2022"},"n_packages":0,"n_references":3,"next":{"headline":"nilfs2: fix shift-out-of-bounds/overflow in nilfs_sb2_bad_offset()","id":"CVE-2022-50478"},"packages":[],"prev":{"headline":"ntb_netdev: Use dev_kfree_skb_any() in interrupt context","id":"CVE-2022-50476"},"products":["Linux"],"published":"2025-10-04","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 memory leak in the Linux kernel RTC driver can lead to resource exhaustion and denial of service.","url":"https://insights.sbomify.com/CVE-2022-50477/"}