{"id":"CVE-2026-98780","kind":"vulnerability","aliases":["CVE-2026-98780"],"related":[],"title":"Linux amdgpu driver leaks memory when sysfs registration fails","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu: fix IP instance memory leak on kobject add failure\n\namdgpu_discovery_sysfs_ips() allocates ip_hw_instance with\nkzalloc_flex() and initializes its embedded kobject before calling\nkobject_add().\n\nIf kobject_add() fails, the return value is ignored and execution\ncontinues without dropping the initial kobject reference. The failed\nkobject is not retained in the kset list, so the normal sysfs teardown\npath cannot find it. As a result, ip_hw_instance_release() is never\ncalled and the ip_hw_instance allocation is leaked.\n\nCall kobject_put() when kobject_add() fails so the initial reference is\ndropped and ip_hw_instance_release() can free the allocation. Keep the\nexisting best-effort sysfs behavior by continuing with the remaining IP\nentries after the failed registration.\n\nThe issue was identified by a static analysis tool I developed and\nconfirmed by manual review.\n\n(cherry picked from commit 5c75fbcca8af1096d8d9415b91d8ea6212c22ee1)","summary":"In the Linux kernel's amdgpu graphics driver, a failed kobject_add() during IP discovery sysfs setup skips releasing the object, leaking a small kernel allocation. The sources describe a memory leak with no stated attacker capability.","severity":"low","cvss":null,"epss":null,"exploited":false,"exploited_at":null,"products":[],"ecosystems":[],"tags":["amd-gpu","amdgpu","infrastructure","linux-kernel","self-hosted"],"not_affected_if":["amdgpu-not-loaded","no-amd-gpu"],"how_to_check":"- Run `uname -r` and check whether the kernel includes the amdgpu driver (`lsmod | grep amdgpu`)\n- Compare the running kernel against the upstream fix commit 5c75fbcca8af1096d8d9415b91d8ea6212c22ee1 in your distribution's changelog","fix":"- Update the Linux kernel to a distribution build that includes commit 5c75fbcca8af1096d8d9415b91d8ea6212c22ee1 (version unknown from the sources)","status":"open","published_at":"2026-10-18T16:17:31+00:00","first_seen_at":"2026-10-23T21:57:16+00:00","triaged_at":"2026-10-25T05:15:23+00:00","updated_at":"2026-10-25T05:15:23+00:00","category":"infrastructure","confidence":0.6,"triage":{"at":"2026-10-25T05:15:23Z","model":"claude-haiku-5-5","output":{"fix":"- Update the Linux kernel to a distribution build that includes commit 5c75fbcca8af1096d8d9415b91d8ea6212c22ee1 (version unknown from the sources)","reach":"local","title":"Linux amdgpu driver leaks memory when sysfs registration fails","impact":"low","summary":"In the Linux kernel's amdgpu graphics driver, a failed kobject_add() during IP discovery sysfs setup skips releasing the object, leaking a small kernel allocation. The sources describe a memory leak with no stated attacker capability.","category":"infrastructure","nicknames":[],"who_cares":["linux-kernel","amdgpu","amd-gpu","self-hosted"],"confidence":0.6,"needs_auth":"unknown","worst_case":"small kernel memory leak, no code execution stated","analyst_note":"","how_to_check":"- Run `uname -r` and check whether the kernel includes the amdgpu driver (`lsmod | grep amdgpu`)\n- Compare the running kernel against the upstream fix commit 5c75fbcca8af1096d8d9415b91d8ea6212c22ee1 in your distribution's changelog","needs_analyst":false,"not_affected_if":["no-amd-gpu","amdgpu-not-loaded"],"who_is_affected":"Systems running a Linux kernel with the amdgpu driver loaded, typically machines with AMD Radeon or APU graphics. The leak only occurs when sysfs registration of an IP instance fails, which the sources do not describe as common. Systems without amdgpu hardware can skip it.","user_interaction":"no","needs_special_setup":"unknown","severity_if_unknown":"low"},"cost_usd":0.000653,"input_tokens":3593,"output_tokens":587,"severity_before":"unknown"},"analyst_status":null,"analyst_note":null,"search":"'-2026':11A,14A '-98780':12A,15A '5c75fbcca8af1096d8d9415b91d8ea6212c22ee1':220C 'add':38B,82C,103C,106C,164C 'alloc':52B,88C,156C,180C 'amd':17B 'amd-gpu':16B 'amdgpu':2A,19B,32B,84C 'analysi':207C 'attack':62B 'behavior':188C 'best':185C 'best-effort':184C 'call':101C,150C,159C 'cannot':138C 'capabl':63B 'cherri':216C 'commit':219C 'confirm':212C 'continu':115C,190C 'cve':10A,13A 'describ':55B 'develop':210C 'discoveri':41B,85C 'driver':3A,34B 'drm/amdgpu':74C 'drop':117C,171C 'effort':186C 'embed':98C 'entri':195C 'execut':114C 'exist':183C 'fail':9A,36B,107C,123C,165C,198C 'failur':83C 'find':139C 'fix':75C 'flex':94C 'follow':69C 'free':178C 'gpu':18B 'graphic':33B 'host':26B 'hw':90C,145C,154C,174C 'identifi':203C 'ignor':112C 'infrastructur':20B 'initi':96C,119C,168C 'instanc':77C,91C,146C,155C,175C 'ip':40B,76C,87C,89C,144C,153C,173C,194C 'issu':201C 'keep':181C 'kernel':23B,30B,51B,67C 'kobject':37B,81C,99C,102C,105C,120C,124C,160C,163C 'kset':130C 'kzalloc':93C 'leak':4A,48B,58B,79C,158C 'linux':1A,22B,29B,66C 'linux-kernel':21B 'list':131C 'manual':214C 'memori':5A,57B,78C 'never':149C 'normal':134C 'object':47B 'path':137C 'pick':217C 'put':161C 'refer':121C,169C 'registr':8A,199C 'releas':45B,147C,176C 'remain':193C 'resolv':73C 'result':143C 'retain':127C 'return':109C 'review':215C 'self':25B 'self-host':24B 'setup':43B 'skip':44B 'small':50B 'sourc':54B 'state':61B 'static':206C 'sysf':7A,42B,86C,135C,187C 'teardown':136C 'tool':208C 'valu':110C 'vulner':70C 'without':116C","nicknames":[],"mitigations":[],"who_affected":"Systems running a Linux kernel with the amdgpu driver loaded, typically machines with AMD Radeon or APU graphics. The leak only occurs when sysfs registration of an IP instance fails, which the sources do not describe as common. Systems without amdgpu hardware can skip it.","tier":"C","verified":{},"analyst_revisit_at":null,"first_public_at":"2026-10-18T16:17:31+00:00","kev":null,"cvss_vector":null,"cvss_by":null,"poc_count":0,"sources":[{"source":"nvd","external_id":"CVE-2026-98780","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-98780","severity":null,"published_at":"2026-10-18T16:17:31+00:00","modified_at":"2026-10-21T13:21:46+00:00","first_seen_at":"2026-10-23T21:57:16+00:00","fetched_at":"2026-10-23T22:28:56+00:00","note":null}],"documents":[],"notice":"Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai"}