| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <CAFZT-jKVYbCKMYt8ocahQ_0QV6N_A9VPFS5YYDf7tB2NnDHV_w@mail.gmail.com> Date: Sun, 30 Nov 2014 19:08:07 -0600 From: Ahmed Tamrawi <ahmedtamrawi@...il.com> To: linux-kernel@...r.kernel.org Subject: Possible memory leak in function (reserve_range) not freeing pointer (regionid) Bug Report: https://bugzilla.kernel.org/show_bug.cgi?id=89101 Linux Version [3.17-rc1] Configuration: Default configuration for x86 Function (reserve_range) in file (drivers/pnp/system.c) allocates pointer (regionid) on line (32) and passes it to function (__request_region) through the macros: (request_region) at line (38) or (request_mem_region) at line (40). However, if the resource (res) is allocated through (__request_region) function, then the pointer (res->name) points to the allocated pointer (regionid). Then, there is no way in function (free_resource) or function (release_resource) to free the pointer (regionid) or (res->name). Thus, causing a potential memory leak! Function (reserve_range) source code reference: http://lxr.free-electrons.com/source/drivers/pnp/system.c#L25 Function (free_resource) source code reference:http://lxr.free-electrons.com/source/kernel/resource.c#L172 Function (release_resource) source code reference:http://lxr.free-electrons.com/source/kernel/resource.c#L322 ~Ahmed -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists