idx int64 | project string | commit_id string | project_url string | commit_url string | commit_message string | target int64 | func string | func_hash float64 | file_name string | file_hash float64 | cwe list | cve string | cve_desc string | nvd_url string |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
25,648 | linux | dc0b027dfadfcb8a5504f7d8052754bf8d501ab9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/dc0b027dfadfcb8a5504f7d8052754bf8d501ab9 | NFSv4: Convert the open and close ops to use fmode
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com> | 0 | static int nfs4_xdr_enc_open_noattr(struct rpc_rqst *req, __be32 *p, struct nfs_openargs *args)
{
struct xdr_stream xdr;
struct compound_hdr hdr = {
.nops = 3,
};
int status;
xdr_init_encode(&xdr, &req->rq_snd_buf, p);
encode_compound_hdr(&xdr, &hdr);
status = encode_putfh(&xdr, args->fh);
if (status)
go... | 128,430,056,021,110,400,000,000,000,000,000,000,000 | nfs4xdr.c | 115,855,000,563,496,450,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2011-4324 | The encode_share_access function in fs/nfs/nfs4xdr.c in the Linux kernel before 2.6.29 allows local users to cause a denial of service (BUG and system crash) by using the mknod system call with a pathname on an NFSv4 filesystem. | https://nvd.nist.gov/vuln/detail/CVE-2011-4324 |
25,649 | linux | dc0b027dfadfcb8a5504f7d8052754bf8d501ab9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/dc0b027dfadfcb8a5504f7d8052754bf8d501ab9 | NFSv4: Convert the open and close ops to use fmode
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com> | 0 | static int nfs4_xdr_enc_pathconf(struct rpc_rqst *req, __be32 *p, const struct nfs4_pathconf_arg *args)
{
struct xdr_stream xdr;
struct compound_hdr hdr = {
.nops = 2,
};
int status;
xdr_init_encode(&xdr, &req->rq_snd_buf, p);
encode_compound_hdr(&xdr, &hdr);
status = encode_putfh(&xdr, args->fh);
if (!statu... | 45,939,173,825,770,050,000,000,000,000,000,000,000 | nfs4xdr.c | 115,855,000,563,496,450,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2011-4324 | The encode_share_access function in fs/nfs/nfs4xdr.c in the Linux kernel before 2.6.29 allows local users to cause a denial of service (BUG and system crash) by using the mknod system call with a pathname on an NFSv4 filesystem. | https://nvd.nist.gov/vuln/detail/CVE-2011-4324 |
25,650 | linux | dc0b027dfadfcb8a5504f7d8052754bf8d501ab9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/dc0b027dfadfcb8a5504f7d8052754bf8d501ab9 | NFSv4: Convert the open and close ops to use fmode
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com> | 0 | static int nfs4_xdr_enc_read(struct rpc_rqst *req, __be32 *p, struct nfs_readargs *args)
{
struct rpc_auth *auth = req->rq_task->tk_msg.rpc_cred->cr_auth;
struct xdr_stream xdr;
struct compound_hdr hdr = {
.nops = 2,
};
int replen, status;
xdr_init_encode(&xdr, &req->rq_snd_buf, p);
encode_compound_hdr(&xdr, ... | 266,212,211,015,400,700,000,000,000,000,000,000,000 | nfs4xdr.c | 115,855,000,563,496,450,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2011-4324 | The encode_share_access function in fs/nfs/nfs4xdr.c in the Linux kernel before 2.6.29 allows local users to cause a denial of service (BUG and system crash) by using the mknod system call with a pathname on an NFSv4 filesystem. | https://nvd.nist.gov/vuln/detail/CVE-2011-4324 |
25,651 | linux | dc0b027dfadfcb8a5504f7d8052754bf8d501ab9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/dc0b027dfadfcb8a5504f7d8052754bf8d501ab9 | NFSv4: Convert the open and close ops to use fmode
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com> | 0 | static int nfs4_xdr_enc_readdir(struct rpc_rqst *req, __be32 *p, const struct nfs4_readdir_arg *args)
{
struct xdr_stream xdr;
struct compound_hdr hdr = {
.nops = 2,
};
struct rpc_auth *auth = req->rq_task->tk_msg.rpc_cred->cr_auth;
int replen;
int status;
xdr_init_encode(&xdr, &req->rq_snd_buf, p);
encode_c... | 278,492,152,165,710,840,000,000,000,000,000,000,000 | nfs4xdr.c | 115,855,000,563,496,450,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2011-4324 | The encode_share_access function in fs/nfs/nfs4xdr.c in the Linux kernel before 2.6.29 allows local users to cause a denial of service (BUG and system crash) by using the mknod system call with a pathname on an NFSv4 filesystem. | https://nvd.nist.gov/vuln/detail/CVE-2011-4324 |
25,652 | linux | dc0b027dfadfcb8a5504f7d8052754bf8d501ab9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/dc0b027dfadfcb8a5504f7d8052754bf8d501ab9 | NFSv4: Convert the open and close ops to use fmode
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com> | 0 | static int nfs4_xdr_enc_readlink(struct rpc_rqst *req, __be32 *p, const struct nfs4_readlink *args)
{
struct xdr_stream xdr;
struct compound_hdr hdr = {
.nops = 2,
};
struct rpc_auth *auth = req->rq_task->tk_msg.rpc_cred->cr_auth;
unsigned int replen;
int status;
xdr_init_encode(&xdr, &req->rq_snd_buf, p);
e... | 313,667,121,692,705,020,000,000,000,000,000,000,000 | nfs4xdr.c | 115,855,000,563,496,450,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2011-4324 | The encode_share_access function in fs/nfs/nfs4xdr.c in the Linux kernel before 2.6.29 allows local users to cause a denial of service (BUG and system crash) by using the mknod system call with a pathname on an NFSv4 filesystem. | https://nvd.nist.gov/vuln/detail/CVE-2011-4324 |
25,653 | linux | dc0b027dfadfcb8a5504f7d8052754bf8d501ab9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/dc0b027dfadfcb8a5504f7d8052754bf8d501ab9 | NFSv4: Convert the open and close ops to use fmode
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com> | 0 | static int nfs4_xdr_enc_rename(struct rpc_rqst *req, __be32 *p, const struct nfs4_rename_arg *args)
{
struct xdr_stream xdr;
struct compound_hdr hdr = {
.nops = 7,
};
int status;
xdr_init_encode(&xdr, &req->rq_snd_buf, p);
encode_compound_hdr(&xdr, &hdr);
if ((status = encode_putfh(&xdr, args->old_dir)) != 0)... | 110,481,891,640,576,970,000,000,000,000,000,000,000 | nfs4xdr.c | 115,855,000,563,496,450,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2011-4324 | The encode_share_access function in fs/nfs/nfs4xdr.c in the Linux kernel before 2.6.29 allows local users to cause a denial of service (BUG and system crash) by using the mknod system call with a pathname on an NFSv4 filesystem. | https://nvd.nist.gov/vuln/detail/CVE-2011-4324 |
25,654 | linux | dc0b027dfadfcb8a5504f7d8052754bf8d501ab9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/dc0b027dfadfcb8a5504f7d8052754bf8d501ab9 | NFSv4: Convert the open and close ops to use fmode
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com> | 0 | static int nfs4_xdr_enc_renew(struct rpc_rqst *req, __be32 *p, struct nfs_client *clp)
{
struct xdr_stream xdr;
struct compound_hdr hdr = {
.nops = 1,
};
xdr_init_encode(&xdr, &req->rq_snd_buf, p);
encode_compound_hdr(&xdr, &hdr);
return encode_renew(&xdr, clp);
}
| 323,903,250,448,530,700,000,000,000,000,000,000,000 | nfs4xdr.c | 115,855,000,563,496,450,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2011-4324 | The encode_share_access function in fs/nfs/nfs4xdr.c in the Linux kernel before 2.6.29 allows local users to cause a denial of service (BUG and system crash) by using the mknod system call with a pathname on an NFSv4 filesystem. | https://nvd.nist.gov/vuln/detail/CVE-2011-4324 |
25,655 | linux | dc0b027dfadfcb8a5504f7d8052754bf8d501ab9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/dc0b027dfadfcb8a5504f7d8052754bf8d501ab9 | NFSv4: Convert the open and close ops to use fmode
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com> | 0 | static int nfs4_xdr_enc_server_caps(struct rpc_rqst *req, __be32 *p, const struct nfs_fh *fhandle)
{
struct xdr_stream xdr;
struct compound_hdr hdr = {
.nops = 2,
};
int status;
xdr_init_encode(&xdr, &req->rq_snd_buf, p);
encode_compound_hdr(&xdr, &hdr);
status = encode_putfh(&xdr, fhandle);
if (status == 0)... | 299,362,372,209,234,950,000,000,000,000,000,000,000 | nfs4xdr.c | 115,855,000,563,496,450,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2011-4324 | The encode_share_access function in fs/nfs/nfs4xdr.c in the Linux kernel before 2.6.29 allows local users to cause a denial of service (BUG and system crash) by using the mknod system call with a pathname on an NFSv4 filesystem. | https://nvd.nist.gov/vuln/detail/CVE-2011-4324 |
25,656 | linux | dc0b027dfadfcb8a5504f7d8052754bf8d501ab9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/dc0b027dfadfcb8a5504f7d8052754bf8d501ab9 | NFSv4: Convert the open and close ops to use fmode
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com> | 0 | nfs4_xdr_enc_setacl(struct rpc_rqst *req, __be32 *p, struct nfs_setaclargs *args)
{
struct xdr_stream xdr;
struct compound_hdr hdr = {
.nops = 2,
};
int status;
xdr_init_encode(&xdr, &req->rq_snd_buf, p);
encode_compound_hdr(&xdr, &hdr);
status ... | 198,592,360,435,356,080,000,000,000,000,000,000,000 | nfs4xdr.c | 115,855,000,563,496,450,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2011-4324 | The encode_share_access function in fs/nfs/nfs4xdr.c in the Linux kernel before 2.6.29 allows local users to cause a denial of service (BUG and system crash) by using the mknod system call with a pathname on an NFSv4 filesystem. | https://nvd.nist.gov/vuln/detail/CVE-2011-4324 |
25,657 | linux | dc0b027dfadfcb8a5504f7d8052754bf8d501ab9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/dc0b027dfadfcb8a5504f7d8052754bf8d501ab9 | NFSv4: Convert the open and close ops to use fmode
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com> | 0 | static int nfs4_xdr_enc_setattr(struct rpc_rqst *req, __be32 *p, struct nfs_setattrargs *args)
{
struct xdr_stream xdr;
struct compound_hdr hdr = {
.nops = 3,
};
int status;
xdr_init_encode(&xdr, &req->rq_snd_buf, p);
encode_compound_hdr(&xdr, &hdr);
... | 230,766,966,131,595,630,000,000,000,000,000,000,000 | nfs4xdr.c | 115,855,000,563,496,450,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2011-4324 | The encode_share_access function in fs/nfs/nfs4xdr.c in the Linux kernel before 2.6.29 allows local users to cause a denial of service (BUG and system crash) by using the mknod system call with a pathname on an NFSv4 filesystem. | https://nvd.nist.gov/vuln/detail/CVE-2011-4324 |
25,658 | linux | dc0b027dfadfcb8a5504f7d8052754bf8d501ab9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/dc0b027dfadfcb8a5504f7d8052754bf8d501ab9 | NFSv4: Convert the open and close ops to use fmode
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com> | 0 | static int nfs4_xdr_enc_setclientid(struct rpc_rqst *req, __be32 *p, struct nfs4_setclientid *sc)
{
struct xdr_stream xdr;
struct compound_hdr hdr = {
.nops = 1,
};
xdr_init_encode(&xdr, &req->rq_snd_buf, p);
encode_compound_hdr(&xdr, &hdr);
return encode_setclientid(&xdr, sc);
}
| 161,305,599,547,416,660,000,000,000,000,000,000,000 | nfs4xdr.c | 115,855,000,563,496,450,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2011-4324 | The encode_share_access function in fs/nfs/nfs4xdr.c in the Linux kernel before 2.6.29 allows local users to cause a denial of service (BUG and system crash) by using the mknod system call with a pathname on an NFSv4 filesystem. | https://nvd.nist.gov/vuln/detail/CVE-2011-4324 |
25,659 | linux | dc0b027dfadfcb8a5504f7d8052754bf8d501ab9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/dc0b027dfadfcb8a5504f7d8052754bf8d501ab9 | NFSv4: Convert the open and close ops to use fmode
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com> | 0 | static int nfs4_xdr_enc_setclientid_confirm(struct rpc_rqst *req, __be32 *p, struct nfs_client *clp)
{
struct xdr_stream xdr;
struct compound_hdr hdr = {
.nops = 3,
};
const u32 lease_bitmap[2] = { FATTR4_WORD0_LEASE_TIME, 0 };
int status;
xdr_init_encode(&xdr, &req->rq_snd_buf, p);
encode_compound_hdr(&xdr, ... | 245,880,984,686,516,770,000,000,000,000,000,000,000 | nfs4xdr.c | 115,855,000,563,496,450,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2011-4324 | The encode_share_access function in fs/nfs/nfs4xdr.c in the Linux kernel before 2.6.29 allows local users to cause a denial of service (BUG and system crash) by using the mknod system call with a pathname on an NFSv4 filesystem. | https://nvd.nist.gov/vuln/detail/CVE-2011-4324 |
25,660 | linux | dc0b027dfadfcb8a5504f7d8052754bf8d501ab9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/dc0b027dfadfcb8a5504f7d8052754bf8d501ab9 | NFSv4: Convert the open and close ops to use fmode
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com> | 0 | static int nfs4_xdr_enc_statfs(struct rpc_rqst *req, __be32 *p, const struct nfs4_statfs_arg *args)
{
struct xdr_stream xdr;
struct compound_hdr hdr = {
.nops = 2,
};
int status;
xdr_init_encode(&xdr, &req->rq_snd_buf, p);
encode_compound_hdr(&xdr, &hdr);
status = encode_putfh(&xdr, args->fh);
if (status == ... | 177,197,086,546,166,600,000,000,000,000,000,000,000 | nfs4xdr.c | 115,855,000,563,496,450,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2011-4324 | The encode_share_access function in fs/nfs/nfs4xdr.c in the Linux kernel before 2.6.29 allows local users to cause a denial of service (BUG and system crash) by using the mknod system call with a pathname on an NFSv4 filesystem. | https://nvd.nist.gov/vuln/detail/CVE-2011-4324 |
25,661 | linux | dc0b027dfadfcb8a5504f7d8052754bf8d501ab9 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/dc0b027dfadfcb8a5504f7d8052754bf8d501ab9 | NFSv4: Convert the open and close ops to use fmode
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com> | 0 | static int nfs4_xdr_enc_write(struct rpc_rqst *req, __be32 *p, struct nfs_writeargs *args)
{
struct xdr_stream xdr;
struct compound_hdr hdr = {
.nops = 3,
};
int status;
xdr_init_encode(&xdr, &req->rq_snd_buf, p);
encode_compound_hdr(&xdr, &hdr);
status = encode_putfh(&xdr, args->fh);
if (status)
goto out;... | 56,611,257,553,951,820,000,000,000,000,000,000,000 | nfs4xdr.c | 115,855,000,563,496,450,000,000,000,000,000,000,000 | [
"CWE-703"
] | CVE-2011-4324 | The encode_share_access function in fs/nfs/nfs4xdr.c in the Linux kernel before 2.6.29 allows local users to cause a denial of service (BUG and system crash) by using the mknod system call with a pathname on an NFSv4 filesystem. | https://nvd.nist.gov/vuln/detail/CVE-2011-4324 |
26,679 | linux | 56c6a8a4aadca809e04276eabe5552935c51387f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/56c6a8a4aadca809e04276eabe5552935c51387f | None | 0 | static void check_panic_on_oom(enum oom_constraint constraint, gfp_t gfp_mask,
int order, const nodemask_t *nodemask)
{
if (likely(!sysctl_panic_on_oom))
return;
if (sysctl_panic_on_oom != 2) {
/*
* panic_on_oom == 1 only affects CONSTRAINT_NONE, the kernel
* does not panic for cpuset, mempolicy, or mem... | 190,082,961,396,397,650,000,000,000,000,000,000,000 | None | null | [
"CWE-189"
] | CVE-2011-4097 | Integer overflow in the oom_badness function in mm/oom_kill.c in the Linux kernel before 3.1.8 on 64-bit platforms allows local users to cause a denial of service (memory consumption or process termination) by using a certain large amount of memory. | https://nvd.nist.gov/vuln/detail/CVE-2011-4097 |
26,680 | linux | 56c6a8a4aadca809e04276eabe5552935c51387f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/56c6a8a4aadca809e04276eabe5552935c51387f | None | 0 | static void clear_system_oom(void)
{
struct zone *zone;
spin_lock(&zone_scan_lock);
for_each_populated_zone(zone)
zone_clear_flag(zone, ZONE_OOM_LOCKED);
spin_unlock(&zone_scan_lock);
}
| 295,585,745,790,716,780,000,000,000,000,000,000,000 | None | null | [
"CWE-189"
] | CVE-2011-4097 | Integer overflow in the oom_badness function in mm/oom_kill.c in the Linux kernel before 3.1.8 on 64-bit platforms allows local users to cause a denial of service (memory consumption or process termination) by using a certain large amount of memory. | https://nvd.nist.gov/vuln/detail/CVE-2011-4097 |
26,681 | linux | 56c6a8a4aadca809e04276eabe5552935c51387f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/56c6a8a4aadca809e04276eabe5552935c51387f | None | 0 | void clear_zonelist_oom(struct zonelist *zonelist, gfp_t gfp_mask)
{
struct zoneref *z;
struct zone *zone;
spin_lock(&zone_scan_lock);
for_each_zone_zonelist(zone, z, zonelist, gfp_zone(gfp_mask)) {
zone_clear_flag(zone, ZONE_OOM_LOCKED);
}
spin_unlock(&zone_scan_lock);
}
| 14,276,350,202,442,405,000,000,000,000,000,000,000 | None | null | [
"CWE-189"
] | CVE-2011-4097 | Integer overflow in the oom_badness function in mm/oom_kill.c in the Linux kernel before 3.1.8 on 64-bit platforms allows local users to cause a denial of service (memory consumption or process termination) by using a certain large amount of memory. | https://nvd.nist.gov/vuln/detail/CVE-2011-4097 |
26,682 | linux | 56c6a8a4aadca809e04276eabe5552935c51387f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/56c6a8a4aadca809e04276eabe5552935c51387f | None | 0 | static enum oom_constraint constrained_alloc(struct zonelist *zonelist,
gfp_t gfp_mask, nodemask_t *nodemask,
unsigned long *totalpages)
{
struct zone *zone;
struct zoneref *z;
enum zone_type high_zoneidx = gfp_zone(gfp_mask);
bool cpuset_limited = false;
int nid;
/* Default to all available memory */
*... | 107,825,572,150,740,530,000,000,000,000,000,000,000 | None | null | [
"CWE-189"
] | CVE-2011-4097 | Integer overflow in the oom_badness function in mm/oom_kill.c in the Linux kernel before 3.1.8 on 64-bit platforms allows local users to cause a denial of service (memory consumption or process termination) by using a certain large amount of memory. | https://nvd.nist.gov/vuln/detail/CVE-2011-4097 |
26,683 | linux | 56c6a8a4aadca809e04276eabe5552935c51387f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/56c6a8a4aadca809e04276eabe5552935c51387f | None | 0 | static enum oom_constraint constrained_alloc(struct zonelist *zonelist,
gfp_t gfp_mask, nodemask_t *nodemask,
unsigned long *totalpages)
{
*totalpages = totalram_pages + total_swap_pages;
return CONSTRAINT_NONE;
}
| 231,214,244,877,098,180,000,000,000,000,000,000,000 | None | null | [
"CWE-189"
] | CVE-2011-4097 | Integer overflow in the oom_badness function in mm/oom_kill.c in the Linux kernel before 3.1.8 on 64-bit platforms allows local users to cause a denial of service (memory consumption or process termination) by using a certain large amount of memory. | https://nvd.nist.gov/vuln/detail/CVE-2011-4097 |
26,684 | linux | 56c6a8a4aadca809e04276eabe5552935c51387f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/56c6a8a4aadca809e04276eabe5552935c51387f | None | 0 | static void dump_header(struct task_struct *p, gfp_t gfp_mask, int order,
struct mem_cgroup *mem, const nodemask_t *nodemask)
{
task_lock(current);
pr_warning("%s invoked oom-killer: gfp_mask=0x%x, order=%d, "
"oom_adj=%d, oom_score_adj=%d\n",
current->comm, gfp_mask, order, current->signal->oom_adj,
current... | 76,309,025,908,836,130,000,000,000,000,000,000,000 | None | null | [
"CWE-189"
] | CVE-2011-4097 | Integer overflow in the oom_badness function in mm/oom_kill.c in the Linux kernel before 3.1.8 on 64-bit platforms allows local users to cause a denial of service (memory consumption or process termination) by using a certain large amount of memory. | https://nvd.nist.gov/vuln/detail/CVE-2011-4097 |
26,685 | linux | 56c6a8a4aadca809e04276eabe5552935c51387f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/56c6a8a4aadca809e04276eabe5552935c51387f | None | 0 | static void dump_tasks(const struct mem_cgroup *mem, const nodemask_t *nodemask)
{
struct task_struct *p;
struct task_struct *task;
pr_info("[ pid ] uid tgid total_vm rss cpu oom_adj oom_score_adj name\n");
for_each_process(p) {
if (oom_unkillable_task(p, mem, nodemask))
continue;
task = find_lock_... | 223,663,658,514,528,070,000,000,000,000,000,000,000 | None | null | [
"CWE-189"
] | CVE-2011-4097 | Integer overflow in the oom_badness function in mm/oom_kill.c in the Linux kernel before 3.1.8 on 64-bit platforms allows local users to cause a denial of service (memory consumption or process termination) by using a certain large amount of memory. | https://nvd.nist.gov/vuln/detail/CVE-2011-4097 |
26,686 | linux | 56c6a8a4aadca809e04276eabe5552935c51387f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/56c6a8a4aadca809e04276eabe5552935c51387f | None | 0 | struct task_struct *find_lock_task_mm(struct task_struct *p)
{
struct task_struct *t = p;
do {
task_lock(t);
if (likely(t->mm))
return t;
task_unlock(t);
} while_each_thread(p, t);
return NULL;
}
| 333,964,243,737,416,650,000,000,000,000,000,000,000 | None | null | [
"CWE-189"
] | CVE-2011-4097 | Integer overflow in the oom_badness function in mm/oom_kill.c in the Linux kernel before 3.1.8 on 64-bit platforms allows local users to cause a denial of service (memory consumption or process termination) by using a certain large amount of memory. | https://nvd.nist.gov/vuln/detail/CVE-2011-4097 |
26,687 | linux | 56c6a8a4aadca809e04276eabe5552935c51387f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/56c6a8a4aadca809e04276eabe5552935c51387f | None | 0 | void mem_cgroup_out_of_memory(struct mem_cgroup *mem, gfp_t gfp_mask)
{
unsigned long limit;
unsigned int points = 0;
struct task_struct *p;
/*
* If current has a pending SIGKILL, then automatically select it. The
* goal is to allow it to allocate so that it may quickly exit and free
* its memory.
*/
if ... | 114,350,307,290,062,370,000,000,000,000,000,000,000 | None | null | [
"CWE-189"
] | CVE-2011-4097 | Integer overflow in the oom_badness function in mm/oom_kill.c in the Linux kernel before 3.1.8 on 64-bit platforms allows local users to cause a denial of service (memory consumption or process termination) by using a certain large amount of memory. | https://nvd.nist.gov/vuln/detail/CVE-2011-4097 |
26,688 | linux | 56c6a8a4aadca809e04276eabe5552935c51387f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/56c6a8a4aadca809e04276eabe5552935c51387f | None | 0 | static int oom_kill_task(struct task_struct *p, struct mem_cgroup *mem)
{
struct task_struct *q;
struct mm_struct *mm;
p = find_lock_task_mm(p);
if (!p)
return 1;
/* mm cannot be safely dereferenced after task_unlock(p) */
mm = p->mm;
pr_err("Killed process %d (%s) total-vm:%lukB, anon-rss:%lukB, file-rss:%... | 328,277,872,381,148,300,000,000,000,000,000,000,000 | None | null | [
"CWE-189"
] | CVE-2011-4097 | Integer overflow in the oom_badness function in mm/oom_kill.c in the Linux kernel before 3.1.8 on 64-bit platforms allows local users to cause a denial of service (memory consumption or process termination) by using a certain large amount of memory. | https://nvd.nist.gov/vuln/detail/CVE-2011-4097 |
26,689 | linux | 56c6a8a4aadca809e04276eabe5552935c51387f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/56c6a8a4aadca809e04276eabe5552935c51387f | None | 0 | void out_of_memory(struct zonelist *zonelist, gfp_t gfp_mask,
int order, nodemask_t *nodemask)
{
const nodemask_t *mpol_mask;
struct task_struct *p;
unsigned long totalpages;
unsigned long freed = 0;
unsigned int points;
enum oom_constraint constraint = CONSTRAINT_NONE;
int killed = 0;
blocking_notifier_call... | 95,121,212,641,769,130,000,000,000,000,000,000,000 | None | null | [
"CWE-189"
] | CVE-2011-4097 | Integer overflow in the oom_badness function in mm/oom_kill.c in the Linux kernel before 3.1.8 on 64-bit platforms allows local users to cause a denial of service (memory consumption or process termination) by using a certain large amount of memory. | https://nvd.nist.gov/vuln/detail/CVE-2011-4097 |
26,690 | linux | 56c6a8a4aadca809e04276eabe5552935c51387f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/56c6a8a4aadca809e04276eabe5552935c51387f | None | 0 | void pagefault_out_of_memory(void)
{
if (try_set_system_oom()) {
out_of_memory(NULL, 0, 0, NULL);
clear_system_oom();
}
if (!test_thread_flag(TIF_MEMDIE))
schedule_timeout_uninterruptible(1);
}
| 12,849,426,892,044,612,000,000,000,000,000,000,000 | None | null | [
"CWE-189"
] | CVE-2011-4097 | Integer overflow in the oom_badness function in mm/oom_kill.c in the Linux kernel before 3.1.8 on 64-bit platforms allows local users to cause a denial of service (memory consumption or process termination) by using a certain large amount of memory. | https://nvd.nist.gov/vuln/detail/CVE-2011-4097 |
26,691 | linux | 56c6a8a4aadca809e04276eabe5552935c51387f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/56c6a8a4aadca809e04276eabe5552935c51387f | None | 0 | int register_oom_notifier(struct notifier_block *nb)
{
return blocking_notifier_chain_register(&oom_notify_list, nb);
}
| 179,812,897,207,634,670,000,000,000,000,000,000,000 | oom_kill.c | 76,761,435,979,865,940,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2011-4097 | Integer overflow in the oom_badness function in mm/oom_kill.c in the Linux kernel before 3.1.8 on 64-bit platforms allows local users to cause a denial of service (memory consumption or process termination) by using a certain large amount of memory. | https://nvd.nist.gov/vuln/detail/CVE-2011-4097 |
26,692 | linux | 56c6a8a4aadca809e04276eabe5552935c51387f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/56c6a8a4aadca809e04276eabe5552935c51387f | None | 0 | static struct task_struct *select_bad_process(unsigned int *ppoints,
unsigned long totalpages, struct mem_cgroup *mem,
const nodemask_t *nodemask)
{
struct task_struct *g, *p;
struct task_struct *chosen = NULL;
*ppoints = 0;
do_each_thread(g, p) {
unsigned int points;
if (p->exit_state)
continue;
if ... | 174,436,113,161,615,970,000,000,000,000,000,000,000 | None | null | [
"CWE-189"
] | CVE-2011-4097 | Integer overflow in the oom_badness function in mm/oom_kill.c in the Linux kernel before 3.1.8 on 64-bit platforms allows local users to cause a denial of service (memory consumption or process termination) by using a certain large amount of memory. | https://nvd.nist.gov/vuln/detail/CVE-2011-4097 |
26,693 | linux | 56c6a8a4aadca809e04276eabe5552935c51387f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/56c6a8a4aadca809e04276eabe5552935c51387f | None | 0 | int test_set_oom_score_adj(int new_val)
{
struct sighand_struct *sighand = current->sighand;
int old_val;
spin_lock_irq(&sighand->siglock);
old_val = current->signal->oom_score_adj;
if (new_val != old_val) {
if (new_val == OOM_SCORE_ADJ_MIN)
atomic_inc(¤t->mm->oom_disable_count);
else if (old_val == ... | 23,988,703,523,563,903,000,000,000,000,000,000,000 | None | null | [
"CWE-189"
] | CVE-2011-4097 | Integer overflow in the oom_badness function in mm/oom_kill.c in the Linux kernel before 3.1.8 on 64-bit platforms allows local users to cause a denial of service (memory consumption or process termination) by using a certain large amount of memory. | https://nvd.nist.gov/vuln/detail/CVE-2011-4097 |
26,694 | linux | 56c6a8a4aadca809e04276eabe5552935c51387f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/56c6a8a4aadca809e04276eabe5552935c51387f | None | 0 | static int try_set_system_oom(void)
{
struct zone *zone;
int ret = 1;
spin_lock(&zone_scan_lock);
for_each_populated_zone(zone)
if (zone_is_oom_locked(zone)) {
ret = 0;
goto out;
}
for_each_populated_zone(zone)
zone_set_flag(zone, ZONE_OOM_LOCKED);
out:
spin_unlock(&zone_scan_lock);
return ret;
}
| 143,083,474,643,946,510,000,000,000,000,000,000,000 | None | null | [
"CWE-189"
] | CVE-2011-4097 | Integer overflow in the oom_badness function in mm/oom_kill.c in the Linux kernel before 3.1.8 on 64-bit platforms allows local users to cause a denial of service (memory consumption or process termination) by using a certain large amount of memory. | https://nvd.nist.gov/vuln/detail/CVE-2011-4097 |
26,695 | linux | 56c6a8a4aadca809e04276eabe5552935c51387f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/56c6a8a4aadca809e04276eabe5552935c51387f | None | 0 | int try_set_zonelist_oom(struct zonelist *zonelist, gfp_t gfp_mask)
{
struct zoneref *z;
struct zone *zone;
int ret = 1;
spin_lock(&zone_scan_lock);
for_each_zone_zonelist(zone, z, zonelist, gfp_zone(gfp_mask)) {
if (zone_is_oom_locked(zone)) {
ret = 0;
goto out;
}
}
for_each_zone_zonelist(zone, z, z... | 76,585,029,226,120,870,000,000,000,000,000,000,000 | None | null | [
"CWE-189"
] | CVE-2011-4097 | Integer overflow in the oom_badness function in mm/oom_kill.c in the Linux kernel before 3.1.8 on 64-bit platforms allows local users to cause a denial of service (memory consumption or process termination) by using a certain large amount of memory. | https://nvd.nist.gov/vuln/detail/CVE-2011-4097 |
26,696 | linux | 56c6a8a4aadca809e04276eabe5552935c51387f | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/56c6a8a4aadca809e04276eabe5552935c51387f | None | 0 | int unregister_oom_notifier(struct notifier_block *nb)
{
return blocking_notifier_chain_unregister(&oom_notify_list, nb);
}
| 313,481,037,400,562,930,000,000,000,000,000,000,000 | oom_kill.c | 76,761,435,979,865,940,000,000,000,000,000,000,000 | [
"CWE-189"
] | CVE-2011-4097 | Integer overflow in the oom_badness function in mm/oom_kill.c in the Linux kernel before 3.1.8 on 64-bit platforms allows local users to cause a denial of service (memory consumption or process termination) by using a certain large amount of memory. | https://nvd.nist.gov/vuln/detail/CVE-2011-4097 |
26,697 | linux | 15291164b22a357cb211b618adfef4fa82fc0de3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/15291164b22a357cb211b618adfef4fa82fc0de3 | jbd2: clear BH_Delay & BH_Unwritten in journal_unmap_buffer
journal_unmap_buffer()'s zap_buffer: code clears a lot of buffer head
state ala discard_buffer(), but does not touch _Delay or _Unwritten as
discard_buffer() does.
This can be problematic in some areas of the ext4 code which assume
that if they have found a ... | 0 | __blist_add_buffer(struct journal_head **list, struct journal_head *jh)
{
if (!*list) {
jh->b_tnext = jh->b_tprev = jh;
*list = jh;
} else {
/* Insert at the tail of the list to preserve order */
struct journal_head *first = *list, *last = first->b_tprev;
jh->b_tprev = last;
jh->b_tnext = first;
last->b... | 322,318,330,584,105,230,000,000,000,000,000,000,000 | transaction.c | 312,279,320,265,495,400,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-4086 | The journal_unmap_buffer function in fs/jbd2/transaction.c in the Linux kernel before 3.3.1 does not properly handle the _Delay and _Unwritten buffer head states, which allows local users to cause a denial of service (system crash) by leveraging the presence of an ext4 filesystem that was mounted with a journal. | https://nvd.nist.gov/vuln/detail/CVE-2011-4086 |
26,698 | linux | 15291164b22a357cb211b618adfef4fa82fc0de3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/15291164b22a357cb211b618adfef4fa82fc0de3 | jbd2: clear BH_Delay & BH_Unwritten in journal_unmap_buffer
journal_unmap_buffer()'s zap_buffer: code clears a lot of buffer head
state ala discard_buffer(), but does not touch _Delay or _Unwritten as
discard_buffer() does.
This can be problematic in some areas of the ext4 code which assume
that if they have found a ... | 0 | static int __dispose_buffer(struct journal_head *jh, transaction_t *transaction)
{
int may_free = 1;
struct buffer_head *bh = jh2bh(jh);
if (jh->b_cp_transaction) {
JBUFFER_TRACE(jh, "on running+cp transaction");
__jbd2_journal_temp_unlink_buffer(jh);
/*
* We don't want to write the buffer anymore, clear t... | 253,471,407,923,956,500,000,000,000,000,000,000,000 | transaction.c | 312,279,320,265,495,400,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-4086 | The journal_unmap_buffer function in fs/jbd2/transaction.c in the Linux kernel before 3.3.1 does not properly handle the _Delay and _Unwritten buffer head states, which allows local users to cause a denial of service (system crash) by leveraging the presence of an ext4 filesystem that was mounted with a journal. | https://nvd.nist.gov/vuln/detail/CVE-2011-4086 |
26,699 | linux | 15291164b22a357cb211b618adfef4fa82fc0de3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/15291164b22a357cb211b618adfef4fa82fc0de3 | jbd2: clear BH_Delay & BH_Unwritten in journal_unmap_buffer
journal_unmap_buffer()'s zap_buffer: code clears a lot of buffer head
state ala discard_buffer(), but does not touch _Delay or _Unwritten as
discard_buffer() does.
This can be problematic in some areas of the ext4 code which assume
that if they have found a ... | 0 | void __jbd2_journal_file_buffer(struct journal_head *jh,
transaction_t *transaction, int jlist)
{
struct journal_head **list = NULL;
int was_dirty = 0;
struct buffer_head *bh = jh2bh(jh);
J_ASSERT_JH(jh, jbd_is_locked_bh_state(bh));
assert_spin_locked(&transaction->t_journal->j_list_lock);
J_ASSERT_JH(jh, jh... | 107,356,606,458,021,360,000,000,000,000,000,000,000 | transaction.c | 312,279,320,265,495,400,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-4086 | The journal_unmap_buffer function in fs/jbd2/transaction.c in the Linux kernel before 3.3.1 does not properly handle the _Delay and _Unwritten buffer head states, which allows local users to cause a denial of service (system crash) by leveraging the presence of an ext4 filesystem that was mounted with a journal. | https://nvd.nist.gov/vuln/detail/CVE-2011-4086 |
26,700 | linux | 15291164b22a357cb211b618adfef4fa82fc0de3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/15291164b22a357cb211b618adfef4fa82fc0de3 | jbd2: clear BH_Delay & BH_Unwritten in journal_unmap_buffer
journal_unmap_buffer()'s zap_buffer: code clears a lot of buffer head
state ala discard_buffer(), but does not touch _Delay or _Unwritten as
discard_buffer() does.
This can be problematic in some areas of the ext4 code which assume
that if they have found a ... | 0 | void __jbd2_journal_refile_buffer(struct journal_head *jh)
{
int was_dirty, jlist;
struct buffer_head *bh = jh2bh(jh);
J_ASSERT_JH(jh, jbd_is_locked_bh_state(bh));
if (jh->b_transaction)
assert_spin_locked(&jh->b_transaction->t_journal->j_list_lock);
/* If the buffer is now unused, just drop it. */
if (jh->b_... | 303,737,861,136,100,200,000,000,000,000,000,000,000 | transaction.c | 312,279,320,265,495,400,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-4086 | The journal_unmap_buffer function in fs/jbd2/transaction.c in the Linux kernel before 3.3.1 does not properly handle the _Delay and _Unwritten buffer head states, which allows local users to cause a denial of service (system crash) by leveraging the presence of an ext4 filesystem that was mounted with a journal. | https://nvd.nist.gov/vuln/detail/CVE-2011-4086 |
26,701 | linux | 15291164b22a357cb211b618adfef4fa82fc0de3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/15291164b22a357cb211b618adfef4fa82fc0de3 | jbd2: clear BH_Delay & BH_Unwritten in journal_unmap_buffer
journal_unmap_buffer()'s zap_buffer: code clears a lot of buffer head
state ala discard_buffer(), but does not touch _Delay or _Unwritten as
discard_buffer() does.
This can be problematic in some areas of the ext4 code which assume
that if they have found a ... | 0 | void __jbd2_journal_temp_unlink_buffer(struct journal_head *jh)
{
struct journal_head **list = NULL;
transaction_t *transaction;
struct buffer_head *bh = jh2bh(jh);
J_ASSERT_JH(jh, jbd_is_locked_bh_state(bh));
transaction = jh->b_transaction;
if (transaction)
assert_spin_locked(&transaction->t_journal->j_list_... | 277,288,135,893,281,740,000,000,000,000,000,000,000 | transaction.c | 312,279,320,265,495,400,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-4086 | The journal_unmap_buffer function in fs/jbd2/transaction.c in the Linux kernel before 3.3.1 does not properly handle the _Delay and _Unwritten buffer head states, which allows local users to cause a denial of service (system crash) by leveraging the presence of an ext4 filesystem that was mounted with a journal. | https://nvd.nist.gov/vuln/detail/CVE-2011-4086 |
26,702 | linux | 15291164b22a357cb211b618adfef4fa82fc0de3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/15291164b22a357cb211b618adfef4fa82fc0de3 | jbd2: clear BH_Delay & BH_Unwritten in journal_unmap_buffer
journal_unmap_buffer()'s zap_buffer: code clears a lot of buffer head
state ala discard_buffer(), but does not touch _Delay or _Unwritten as
discard_buffer() does.
This can be problematic in some areas of the ext4 code which assume
that if they have found a ... | 0 | static void __jbd2_journal_unfile_buffer(struct journal_head *jh)
{
__jbd2_journal_temp_unlink_buffer(jh);
jh->b_transaction = NULL;
jbd2_journal_put_journal_head(jh);
}
| 290,343,857,631,212,830,000,000,000,000,000,000,000 | transaction.c | 312,279,320,265,495,400,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-4086 | The journal_unmap_buffer function in fs/jbd2/transaction.c in the Linux kernel before 3.3.1 does not properly handle the _Delay and _Unwritten buffer head states, which allows local users to cause a denial of service (system crash) by leveraging the presence of an ext4 filesystem that was mounted with a journal. | https://nvd.nist.gov/vuln/detail/CVE-2011-4086 |
26,703 | linux | 15291164b22a357cb211b618adfef4fa82fc0de3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/15291164b22a357cb211b618adfef4fa82fc0de3 | jbd2: clear BH_Delay & BH_Unwritten in journal_unmap_buffer
journal_unmap_buffer()'s zap_buffer: code clears a lot of buffer head
state ala discard_buffer(), but does not touch _Delay or _Unwritten as
discard_buffer() does.
This can be problematic in some areas of the ext4 code which assume
that if they have found a ... | 0 | __journal_try_to_free_buffer(journal_t *journal, struct buffer_head *bh)
{
struct journal_head *jh;
jh = bh2jh(bh);
if (buffer_locked(bh) || buffer_dirty(bh))
goto out;
if (jh->b_next_transaction != NULL)
goto out;
spin_lock(&journal->j_list_lock);
if (jh->b_cp_transaction != NULL && jh->b_transaction == ... | 170,395,229,388,510,000,000,000,000,000,000,000,000 | transaction.c | 312,279,320,265,495,400,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-4086 | The journal_unmap_buffer function in fs/jbd2/transaction.c in the Linux kernel before 3.3.1 does not properly handle the _Delay and _Unwritten buffer head states, which allows local users to cause a denial of service (system crash) by leveraging the presence of an ext4 filesystem that was mounted with a journal. | https://nvd.nist.gov/vuln/detail/CVE-2011-4086 |
26,704 | linux | 15291164b22a357cb211b618adfef4fa82fc0de3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/15291164b22a357cb211b618adfef4fa82fc0de3 | jbd2: clear BH_Delay & BH_Unwritten in journal_unmap_buffer
journal_unmap_buffer()'s zap_buffer: code clears a lot of buffer head
state ala discard_buffer(), but does not touch _Delay or _Unwritten as
discard_buffer() does.
This can be problematic in some areas of the ext4 code which assume
that if they have found a ... | 0 | do_get_write_access(handle_t *handle, struct journal_head *jh,
int force_copy)
{
struct buffer_head *bh;
transaction_t *transaction;
journal_t *journal;
int error;
char *frozen_buffer = NULL;
int need_copy = 0;
if (is_handle_aborted(handle))
return -EROFS;
transaction = handle->h_transaction;
journal = ... | 6,636,636,386,222,180,000,000,000,000,000,000,000 | transaction.c | 312,279,320,265,495,400,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-4086 | The journal_unmap_buffer function in fs/jbd2/transaction.c in the Linux kernel before 3.3.1 does not properly handle the _Delay and _Unwritten buffer head states, which allows local users to cause a denial of service (system crash) by leveraging the presence of an ext4 filesystem that was mounted with a journal. | https://nvd.nist.gov/vuln/detail/CVE-2011-4086 |
26,705 | linux | 15291164b22a357cb211b618adfef4fa82fc0de3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/15291164b22a357cb211b618adfef4fa82fc0de3 | jbd2: clear BH_Delay & BH_Unwritten in journal_unmap_buffer
journal_unmap_buffer()'s zap_buffer: code clears a lot of buffer head
state ala discard_buffer(), but does not touch _Delay or _Unwritten as
discard_buffer() does.
This can be problematic in some areas of the ext4 code which assume
that if they have found a ... | 0 | int jbd2__journal_restart(handle_t *handle, int nblocks, gfp_t gfp_mask)
{
transaction_t *transaction = handle->h_transaction;
journal_t *journal = transaction->t_journal;
tid_t tid;
int need_to_start, ret;
/* If we've had an abort of any type, don't even think about
* actually doing the restart! */
if (is_h... | 201,116,875,942,116,000,000,000,000,000,000,000,000 | transaction.c | 312,279,320,265,495,400,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-4086 | The journal_unmap_buffer function in fs/jbd2/transaction.c in the Linux kernel before 3.3.1 does not properly handle the _Delay and _Unwritten buffer head states, which allows local users to cause a denial of service (system crash) by leveraging the presence of an ext4 filesystem that was mounted with a journal. | https://nvd.nist.gov/vuln/detail/CVE-2011-4086 |
26,706 | linux | 15291164b22a357cb211b618adfef4fa82fc0de3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/15291164b22a357cb211b618adfef4fa82fc0de3 | jbd2: clear BH_Delay & BH_Unwritten in journal_unmap_buffer
journal_unmap_buffer()'s zap_buffer: code clears a lot of buffer head
state ala discard_buffer(), but does not touch _Delay or _Unwritten as
discard_buffer() does.
This can be problematic in some areas of the ext4 code which assume
that if they have found a ... | 0 | handle_t *jbd2__journal_start(journal_t *journal, int nblocks, gfp_t gfp_mask)
{
handle_t *handle = journal_current_handle();
int err;
if (!journal)
return ERR_PTR(-EROFS);
if (handle) {
J_ASSERT(handle->h_transaction->t_journal == journal);
handle->h_ref++;
return handle;
}
handle = new_handle(nblocks... | 331,010,526,285,773,200,000,000,000,000,000,000,000 | transaction.c | 312,279,320,265,495,400,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-4086 | The journal_unmap_buffer function in fs/jbd2/transaction.c in the Linux kernel before 3.3.1 does not properly handle the _Delay and _Unwritten buffer head states, which allows local users to cause a denial of service (system crash) by leveraging the presence of an ext4 filesystem that was mounted with a journal. | https://nvd.nist.gov/vuln/detail/CVE-2011-4086 |
26,707 | linux | 15291164b22a357cb211b618adfef4fa82fc0de3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/15291164b22a357cb211b618adfef4fa82fc0de3 | jbd2: clear BH_Delay & BH_Unwritten in journal_unmap_buffer
journal_unmap_buffer()'s zap_buffer: code clears a lot of buffer head
state ala discard_buffer(), but does not touch _Delay or _Unwritten as
discard_buffer() does.
This can be problematic in some areas of the ext4 code which assume
that if they have found a ... | 0 | void jbd2_buffer_frozen_trigger(struct journal_head *jh, void *mapped_data,
struct jbd2_buffer_trigger_type *triggers)
{
struct buffer_head *bh = jh2bh(jh);
if (!triggers || !triggers->t_frozen)
return;
triggers->t_frozen(triggers, bh, mapped_data, bh->b_size);
}
| 243,789,444,114,382,800,000,000,000,000,000,000,000 | transaction.c | 312,279,320,265,495,400,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-4086 | The journal_unmap_buffer function in fs/jbd2/transaction.c in the Linux kernel before 3.3.1 does not properly handle the _Delay and _Unwritten buffer head states, which allows local users to cause a denial of service (system crash) by leveraging the presence of an ext4 filesystem that was mounted with a journal. | https://nvd.nist.gov/vuln/detail/CVE-2011-4086 |
26,708 | linux | 15291164b22a357cb211b618adfef4fa82fc0de3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/15291164b22a357cb211b618adfef4fa82fc0de3 | jbd2: clear BH_Delay & BH_Unwritten in journal_unmap_buffer
journal_unmap_buffer()'s zap_buffer: code clears a lot of buffer head
state ala discard_buffer(), but does not touch _Delay or _Unwritten as
discard_buffer() does.
This can be problematic in some areas of the ext4 code which assume
that if they have found a ... | 0 | int jbd2_journal_begin_ordered_truncate(journal_t *journal,
struct jbd2_inode *jinode,
loff_t new_size)
{
transaction_t *inode_trans, *commit_trans;
int ret = 0;
/* This is a quick check to avoid locking if not necessary */
if (!jinode->i_transaction)
goto out;
/* Locks are here just to force reading ... | 3,802,619,827,984,727,000,000,000,000,000,000,000 | transaction.c | 312,279,320,265,495,400,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-4086 | The journal_unmap_buffer function in fs/jbd2/transaction.c in the Linux kernel before 3.3.1 does not properly handle the _Delay and _Unwritten buffer head states, which allows local users to cause a denial of service (system crash) by leveraging the presence of an ext4 filesystem that was mounted with a journal. | https://nvd.nist.gov/vuln/detail/CVE-2011-4086 |
26,709 | linux | 15291164b22a357cb211b618adfef4fa82fc0de3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/15291164b22a357cb211b618adfef4fa82fc0de3 | jbd2: clear BH_Delay & BH_Unwritten in journal_unmap_buffer
journal_unmap_buffer()'s zap_buffer: code clears a lot of buffer head
state ala discard_buffer(), but does not touch _Delay or _Unwritten as
discard_buffer() does.
This can be problematic in some areas of the ext4 code which assume
that if they have found a ... | 0 | int jbd2_journal_dirty_metadata(handle_t *handle, struct buffer_head *bh)
{
transaction_t *transaction = handle->h_transaction;
journal_t *journal = transaction->t_journal;
struct journal_head *jh = bh2jh(bh);
int ret = 0;
jbd_debug(5, "journal_head %p\n", jh);
JBUFFER_TRACE(jh, "entry");
if (is_handle_aborted(... | 151,871,797,139,250,710,000,000,000,000,000,000,000 | transaction.c | 312,279,320,265,495,400,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-4086 | The journal_unmap_buffer function in fs/jbd2/transaction.c in the Linux kernel before 3.3.1 does not properly handle the _Delay and _Unwritten buffer head states, which allows local users to cause a denial of service (system crash) by leveraging the presence of an ext4 filesystem that was mounted with a journal. | https://nvd.nist.gov/vuln/detail/CVE-2011-4086 |
26,710 | linux | 15291164b22a357cb211b618adfef4fa82fc0de3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/15291164b22a357cb211b618adfef4fa82fc0de3 | jbd2: clear BH_Delay & BH_Unwritten in journal_unmap_buffer
journal_unmap_buffer()'s zap_buffer: code clears a lot of buffer head
state ala discard_buffer(), but does not touch _Delay or _Unwritten as
discard_buffer() does.
This can be problematic in some areas of the ext4 code which assume
that if they have found a ... | 0 | int jbd2_journal_extend(handle_t *handle, int nblocks)
{
transaction_t *transaction = handle->h_transaction;
journal_t *journal = transaction->t_journal;
int result;
int wanted;
result = -EIO;
if (is_handle_aborted(handle))
goto out;
result = 1;
read_lock(&journal->j_state_lock);
/* Don't extend a locked... | 155,847,745,429,571,510,000,000,000,000,000,000,000 | transaction.c | 312,279,320,265,495,400,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-4086 | The journal_unmap_buffer function in fs/jbd2/transaction.c in the Linux kernel before 3.3.1 does not properly handle the _Delay and _Unwritten buffer head states, which allows local users to cause a denial of service (system crash) by leveraging the presence of an ext4 filesystem that was mounted with a journal. | https://nvd.nist.gov/vuln/detail/CVE-2011-4086 |
26,711 | linux | 15291164b22a357cb211b618adfef4fa82fc0de3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/15291164b22a357cb211b618adfef4fa82fc0de3 | jbd2: clear BH_Delay & BH_Unwritten in journal_unmap_buffer
journal_unmap_buffer()'s zap_buffer: code clears a lot of buffer head
state ala discard_buffer(), but does not touch _Delay or _Unwritten as
discard_buffer() does.
This can be problematic in some areas of the ext4 code which assume
that if they have found a ... | 0 | void jbd2_journal_file_buffer(struct journal_head *jh,
transaction_t *transaction, int jlist)
{
jbd_lock_bh_state(jh2bh(jh));
spin_lock(&transaction->t_journal->j_list_lock);
__jbd2_journal_file_buffer(jh, transaction, jlist);
spin_unlock(&transaction->t_journal->j_list_lock);
jbd_unlock_bh_state(jh2bh(jh));
}... | 168,135,807,855,286,330,000,000,000,000,000,000,000 | transaction.c | 312,279,320,265,495,400,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-4086 | The journal_unmap_buffer function in fs/jbd2/transaction.c in the Linux kernel before 3.3.1 does not properly handle the _Delay and _Unwritten buffer head states, which allows local users to cause a denial of service (system crash) by leveraging the presence of an ext4 filesystem that was mounted with a journal. | https://nvd.nist.gov/vuln/detail/CVE-2011-4086 |
26,712 | linux | 15291164b22a357cb211b618adfef4fa82fc0de3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/15291164b22a357cb211b618adfef4fa82fc0de3 | jbd2: clear BH_Delay & BH_Unwritten in journal_unmap_buffer
journal_unmap_buffer()'s zap_buffer: code clears a lot of buffer head
state ala discard_buffer(), but does not touch _Delay or _Unwritten as
discard_buffer() does.
This can be problematic in some areas of the ext4 code which assume
that if they have found a ... | 0 | int jbd2_journal_file_inode(handle_t *handle, struct jbd2_inode *jinode)
{
transaction_t *transaction = handle->h_transaction;
journal_t *journal = transaction->t_journal;
if (is_handle_aborted(handle))
return -EIO;
jbd_debug(4, "Adding inode %lu, tid:%d\n", jinode->i_vfs_inode->i_ino,
transaction->t_tid);
... | 116,074,308,780,545,670,000,000,000,000,000,000,000 | transaction.c | 312,279,320,265,495,400,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-4086 | The journal_unmap_buffer function in fs/jbd2/transaction.c in the Linux kernel before 3.3.1 does not properly handle the _Delay and _Unwritten buffer head states, which allows local users to cause a denial of service (system crash) by leveraging the presence of an ext4 filesystem that was mounted with a journal. | https://nvd.nist.gov/vuln/detail/CVE-2011-4086 |
26,713 | linux | 15291164b22a357cb211b618adfef4fa82fc0de3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/15291164b22a357cb211b618adfef4fa82fc0de3 | jbd2: clear BH_Delay & BH_Unwritten in journal_unmap_buffer
journal_unmap_buffer()'s zap_buffer: code clears a lot of buffer head
state ala discard_buffer(), but does not touch _Delay or _Unwritten as
discard_buffer() does.
This can be problematic in some areas of the ext4 code which assume
that if they have found a ... | 0 | int jbd2_journal_force_commit(journal_t *journal)
{
handle_t *handle;
int ret;
handle = jbd2_journal_start(journal, 1);
if (IS_ERR(handle)) {
ret = PTR_ERR(handle);
} else {
handle->h_sync = 1;
ret = jbd2_journal_stop(handle);
}
return ret;
}
| 109,650,762,857,741,770,000,000,000,000,000,000,000 | transaction.c | 312,279,320,265,495,400,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-4086 | The journal_unmap_buffer function in fs/jbd2/transaction.c in the Linux kernel before 3.3.1 does not properly handle the _Delay and _Unwritten buffer head states, which allows local users to cause a denial of service (system crash) by leveraging the presence of an ext4 filesystem that was mounted with a journal. | https://nvd.nist.gov/vuln/detail/CVE-2011-4086 |
26,714 | linux | 15291164b22a357cb211b618adfef4fa82fc0de3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/15291164b22a357cb211b618adfef4fa82fc0de3 | jbd2: clear BH_Delay & BH_Unwritten in journal_unmap_buffer
journal_unmap_buffer()'s zap_buffer: code clears a lot of buffer head
state ala discard_buffer(), but does not touch _Delay or _Unwritten as
discard_buffer() does.
This can be problematic in some areas of the ext4 code which assume
that if they have found a ... | 0 | int jbd2_journal_forget (handle_t *handle, struct buffer_head *bh)
{
transaction_t *transaction = handle->h_transaction;
journal_t *journal = transaction->t_journal;
struct journal_head *jh;
int drop_reserve = 0;
int err = 0;
int was_modified = 0;
BUFFER_TRACE(bh, "entry");
jbd_lock_bh_state(bh);
spin_lock(&... | 227,086,242,820,184,140,000,000,000,000,000,000,000 | transaction.c | 312,279,320,265,495,400,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-4086 | The journal_unmap_buffer function in fs/jbd2/transaction.c in the Linux kernel before 3.3.1 does not properly handle the _Delay and _Unwritten buffer head states, which allows local users to cause a denial of service (system crash) by leveraging the presence of an ext4 filesystem that was mounted with a journal. | https://nvd.nist.gov/vuln/detail/CVE-2011-4086 |
26,715 | linux | 15291164b22a357cb211b618adfef4fa82fc0de3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/15291164b22a357cb211b618adfef4fa82fc0de3 | jbd2: clear BH_Delay & BH_Unwritten in journal_unmap_buffer
journal_unmap_buffer()'s zap_buffer: code clears a lot of buffer head
state ala discard_buffer(), but does not touch _Delay or _Unwritten as
discard_buffer() does.
This can be problematic in some areas of the ext4 code which assume
that if they have found a ... | 0 | int jbd2_journal_get_create_access(handle_t *handle, struct buffer_head *bh)
{
transaction_t *transaction = handle->h_transaction;
journal_t *journal = transaction->t_journal;
struct journal_head *jh = jbd2_journal_add_journal_head(bh);
int err;
jbd_debug(5, "journal_head %p\n", jh);
err = -EROFS;
if (is_handle... | 278,272,893,484,637,580,000,000,000,000,000,000,000 | transaction.c | 312,279,320,265,495,400,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-4086 | The journal_unmap_buffer function in fs/jbd2/transaction.c in the Linux kernel before 3.3.1 does not properly handle the _Delay and _Unwritten buffer head states, which allows local users to cause a denial of service (system crash) by leveraging the presence of an ext4 filesystem that was mounted with a journal. | https://nvd.nist.gov/vuln/detail/CVE-2011-4086 |
26,716 | linux | 15291164b22a357cb211b618adfef4fa82fc0de3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/15291164b22a357cb211b618adfef4fa82fc0de3 | jbd2: clear BH_Delay & BH_Unwritten in journal_unmap_buffer
journal_unmap_buffer()'s zap_buffer: code clears a lot of buffer head
state ala discard_buffer(), but does not touch _Delay or _Unwritten as
discard_buffer() does.
This can be problematic in some areas of the ext4 code which assume
that if they have found a ... | 0 | int jbd2_journal_get_undo_access(handle_t *handle, struct buffer_head *bh)
{
int err;
struct journal_head *jh = jbd2_journal_add_journal_head(bh);
char *committed_data = NULL;
JBUFFER_TRACE(jh, "entry");
/*
* Do this first --- it can drop the journal lock, so we want to
* make sure that obtaining the committ... | 236,762,051,720,683,420,000,000,000,000,000,000,000 | transaction.c | 312,279,320,265,495,400,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-4086 | The journal_unmap_buffer function in fs/jbd2/transaction.c in the Linux kernel before 3.3.1 does not properly handle the _Delay and _Unwritten buffer head states, which allows local users to cause a denial of service (system crash) by leveraging the presence of an ext4 filesystem that was mounted with a journal. | https://nvd.nist.gov/vuln/detail/CVE-2011-4086 |
26,717 | linux | 15291164b22a357cb211b618adfef4fa82fc0de3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/15291164b22a357cb211b618adfef4fa82fc0de3 | jbd2: clear BH_Delay & BH_Unwritten in journal_unmap_buffer
journal_unmap_buffer()'s zap_buffer: code clears a lot of buffer head
state ala discard_buffer(), but does not touch _Delay or _Unwritten as
discard_buffer() does.
This can be problematic in some areas of the ext4 code which assume
that if they have found a ... | 0 | int jbd2_journal_get_write_access(handle_t *handle, struct buffer_head *bh)
{
struct journal_head *jh = jbd2_journal_add_journal_head(bh);
int rc;
/* We do not want to get caught playing with fields which the
* log thread also manipulates. Make sure that the buffer
* completes any outstanding IO before proceed... | 304,268,655,112,457,830,000,000,000,000,000,000,000 | transaction.c | 312,279,320,265,495,400,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-4086 | The journal_unmap_buffer function in fs/jbd2/transaction.c in the Linux kernel before 3.3.1 does not properly handle the _Delay and _Unwritten buffer head states, which allows local users to cause a denial of service (system crash) by leveraging the presence of an ext4 filesystem that was mounted with a journal. | https://nvd.nist.gov/vuln/detail/CVE-2011-4086 |
26,718 | linux | 15291164b22a357cb211b618adfef4fa82fc0de3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/15291164b22a357cb211b618adfef4fa82fc0de3 | jbd2: clear BH_Delay & BH_Unwritten in journal_unmap_buffer
journal_unmap_buffer()'s zap_buffer: code clears a lot of buffer head
state ala discard_buffer(), but does not touch _Delay or _Unwritten as
discard_buffer() does.
This can be problematic in some areas of the ext4 code which assume
that if they have found a ... | 0 | void jbd2_journal_invalidatepage(journal_t *journal,
struct page *page,
unsigned long offset)
{
struct buffer_head *head, *bh, *next;
unsigned int curr_off = 0;
int may_free = 1;
if (!PageLocked(page))
BUG();
if (!page_has_buffers(page))
return;
/* We will potentially be playing with lists o... | 317,546,676,065,279,050,000,000,000,000,000,000,000 | transaction.c | 312,279,320,265,495,400,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-4086 | The journal_unmap_buffer function in fs/jbd2/transaction.c in the Linux kernel before 3.3.1 does not properly handle the _Delay and _Unwritten buffer head states, which allows local users to cause a denial of service (system crash) by leveraging the presence of an ext4 filesystem that was mounted with a journal. | https://nvd.nist.gov/vuln/detail/CVE-2011-4086 |
26,719 | linux | 15291164b22a357cb211b618adfef4fa82fc0de3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/15291164b22a357cb211b618adfef4fa82fc0de3 | jbd2: clear BH_Delay & BH_Unwritten in journal_unmap_buffer
journal_unmap_buffer()'s zap_buffer: code clears a lot of buffer head
state ala discard_buffer(), but does not touch _Delay or _Unwritten as
discard_buffer() does.
This can be problematic in some areas of the ext4 code which assume
that if they have found a ... | 0 | void jbd2_journal_refile_buffer(journal_t *journal, struct journal_head *jh)
{
struct buffer_head *bh = jh2bh(jh);
/* Get reference so that buffer cannot be freed before we unlock it */
get_bh(bh);
jbd_lock_bh_state(bh);
spin_lock(&journal->j_list_lock);
__jbd2_journal_refile_buffer(jh);
jbd_unlock_bh_state(bh)... | 268,653,027,460,778,800,000,000,000,000,000,000,000 | transaction.c | 312,279,320,265,495,400,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-4086 | The journal_unmap_buffer function in fs/jbd2/transaction.c in the Linux kernel before 3.3.1 does not properly handle the _Delay and _Unwritten buffer head states, which allows local users to cause a denial of service (system crash) by leveraging the presence of an ext4 filesystem that was mounted with a journal. | https://nvd.nist.gov/vuln/detail/CVE-2011-4086 |
26,720 | linux | 15291164b22a357cb211b618adfef4fa82fc0de3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/15291164b22a357cb211b618adfef4fa82fc0de3 | jbd2: clear BH_Delay & BH_Unwritten in journal_unmap_buffer
journal_unmap_buffer()'s zap_buffer: code clears a lot of buffer head
state ala discard_buffer(), but does not touch _Delay or _Unwritten as
discard_buffer() does.
This can be problematic in some areas of the ext4 code which assume
that if they have found a ... | 0 | jbd2_journal_release_buffer(handle_t *handle, struct buffer_head *bh)
{
BUFFER_TRACE(bh, "entry");
}
| 221,634,243,900,007,650,000,000,000,000,000,000,000 | transaction.c | 312,279,320,265,495,400,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-4086 | The journal_unmap_buffer function in fs/jbd2/transaction.c in the Linux kernel before 3.3.1 does not properly handle the _Delay and _Unwritten buffer head states, which allows local users to cause a denial of service (system crash) by leveraging the presence of an ext4 filesystem that was mounted with a journal. | https://nvd.nist.gov/vuln/detail/CVE-2011-4086 |
26,721 | linux | 15291164b22a357cb211b618adfef4fa82fc0de3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/15291164b22a357cb211b618adfef4fa82fc0de3 | jbd2: clear BH_Delay & BH_Unwritten in journal_unmap_buffer
journal_unmap_buffer()'s zap_buffer: code clears a lot of buffer head
state ala discard_buffer(), but does not touch _Delay or _Unwritten as
discard_buffer() does.
This can be problematic in some areas of the ext4 code which assume
that if they have found a ... | 0 | int jbd2_journal_restart(handle_t *handle, int nblocks)
{
return jbd2__journal_restart(handle, nblocks, GFP_NOFS);
}
| 29,377,543,441,265,404,000,000,000,000,000,000,000 | transaction.c | 312,279,320,265,495,400,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-4086 | The journal_unmap_buffer function in fs/jbd2/transaction.c in the Linux kernel before 3.3.1 does not properly handle the _Delay and _Unwritten buffer head states, which allows local users to cause a denial of service (system crash) by leveraging the presence of an ext4 filesystem that was mounted with a journal. | https://nvd.nist.gov/vuln/detail/CVE-2011-4086 |
26,722 | linux | 15291164b22a357cb211b618adfef4fa82fc0de3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/15291164b22a357cb211b618adfef4fa82fc0de3 | jbd2: clear BH_Delay & BH_Unwritten in journal_unmap_buffer
journal_unmap_buffer()'s zap_buffer: code clears a lot of buffer head
state ala discard_buffer(), but does not touch _Delay or _Unwritten as
discard_buffer() does.
This can be problematic in some areas of the ext4 code which assume
that if they have found a ... | 0 | void jbd2_journal_set_triggers(struct buffer_head *bh,
struct jbd2_buffer_trigger_type *type)
{
struct journal_head *jh = bh2jh(bh);
jh->b_triggers = type;
}
| 29,342,953,861,070,253,000,000,000,000,000,000,000 | transaction.c | 312,279,320,265,495,400,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-4086 | The journal_unmap_buffer function in fs/jbd2/transaction.c in the Linux kernel before 3.3.1 does not properly handle the _Delay and _Unwritten buffer head states, which allows local users to cause a denial of service (system crash) by leveraging the presence of an ext4 filesystem that was mounted with a journal. | https://nvd.nist.gov/vuln/detail/CVE-2011-4086 |
26,723 | linux | 15291164b22a357cb211b618adfef4fa82fc0de3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/15291164b22a357cb211b618adfef4fa82fc0de3 | jbd2: clear BH_Delay & BH_Unwritten in journal_unmap_buffer
journal_unmap_buffer()'s zap_buffer: code clears a lot of buffer head
state ala discard_buffer(), but does not touch _Delay or _Unwritten as
discard_buffer() does.
This can be problematic in some areas of the ext4 code which assume
that if they have found a ... | 0 | handle_t *jbd2_journal_start(journal_t *journal, int nblocks)
{
return jbd2__journal_start(journal, nblocks, GFP_NOFS);
}
| 158,248,798,113,404,740,000,000,000,000,000,000,000 | transaction.c | 312,279,320,265,495,400,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-4086 | The journal_unmap_buffer function in fs/jbd2/transaction.c in the Linux kernel before 3.3.1 does not properly handle the _Delay and _Unwritten buffer head states, which allows local users to cause a denial of service (system crash) by leveraging the presence of an ext4 filesystem that was mounted with a journal. | https://nvd.nist.gov/vuln/detail/CVE-2011-4086 |
26,724 | linux | 15291164b22a357cb211b618adfef4fa82fc0de3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/15291164b22a357cb211b618adfef4fa82fc0de3 | jbd2: clear BH_Delay & BH_Unwritten in journal_unmap_buffer
journal_unmap_buffer()'s zap_buffer: code clears a lot of buffer head
state ala discard_buffer(), but does not touch _Delay or _Unwritten as
discard_buffer() does.
This can be problematic in some areas of the ext4 code which assume
that if they have found a ... | 0 | int jbd2_journal_stop(handle_t *handle)
{
transaction_t *transaction = handle->h_transaction;
journal_t *journal = transaction->t_journal;
int err, wait_for_commit = 0;
tid_t tid;
pid_t pid;
J_ASSERT(journal_current_handle() == handle);
if (is_handle_aborted(handle))
err = -EIO;
else {
J_ASSERT(atomic_rea... | 254,919,707,934,128,530,000,000,000,000,000,000,000 | transaction.c | 312,279,320,265,495,400,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-4086 | The journal_unmap_buffer function in fs/jbd2/transaction.c in the Linux kernel before 3.3.1 does not properly handle the _Delay and _Unwritten buffer head states, which allows local users to cause a denial of service (system crash) by leveraging the presence of an ext4 filesystem that was mounted with a journal. | https://nvd.nist.gov/vuln/detail/CVE-2011-4086 |
26,725 | linux | 15291164b22a357cb211b618adfef4fa82fc0de3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/15291164b22a357cb211b618adfef4fa82fc0de3 | jbd2: clear BH_Delay & BH_Unwritten in journal_unmap_buffer
journal_unmap_buffer()'s zap_buffer: code clears a lot of buffer head
state ala discard_buffer(), but does not touch _Delay or _Unwritten as
discard_buffer() does.
This can be problematic in some areas of the ext4 code which assume
that if they have found a ... | 0 | int jbd2_journal_try_to_free_buffers(journal_t *journal,
struct page *page, gfp_t gfp_mask)
{
struct buffer_head *head;
struct buffer_head *bh;
int ret = 0;
J_ASSERT(PageLocked(page));
head = page_buffers(page);
bh = head;
do {
struct journal_head *jh;
/*
* We take our own ref against the journal_h... | 7,522,933,743,349,770,000,000,000,000,000,000,000 | transaction.c | 312,279,320,265,495,400,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-4086 | The journal_unmap_buffer function in fs/jbd2/transaction.c in the Linux kernel before 3.3.1 does not properly handle the _Delay and _Unwritten buffer head states, which allows local users to cause a denial of service (system crash) by leveraging the presence of an ext4 filesystem that was mounted with a journal. | https://nvd.nist.gov/vuln/detail/CVE-2011-4086 |
26,726 | linux | 15291164b22a357cb211b618adfef4fa82fc0de3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/15291164b22a357cb211b618adfef4fa82fc0de3 | jbd2: clear BH_Delay & BH_Unwritten in journal_unmap_buffer
journal_unmap_buffer()'s zap_buffer: code clears a lot of buffer head
state ala discard_buffer(), but does not touch _Delay or _Unwritten as
discard_buffer() does.
This can be problematic in some areas of the ext4 code which assume
that if they have found a ... | 0 | void jbd2_journal_unfile_buffer(journal_t *journal, struct journal_head *jh)
{
struct buffer_head *bh = jh2bh(jh);
/* Get reference so that buffer cannot be freed before we unlock it */
get_bh(bh);
jbd_lock_bh_state(bh);
spin_lock(&journal->j_list_lock);
__jbd2_journal_unfile_buffer(jh);
spin_unlock(&journal->j... | 160,289,028,373,821,930,000,000,000,000,000,000,000 | transaction.c | 312,279,320,265,495,400,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-4086 | The journal_unmap_buffer function in fs/jbd2/transaction.c in the Linux kernel before 3.3.1 does not properly handle the _Delay and _Unwritten buffer head states, which allows local users to cause a denial of service (system crash) by leveraging the presence of an ext4 filesystem that was mounted with a journal. | https://nvd.nist.gov/vuln/detail/CVE-2011-4086 |
26,727 | linux | 15291164b22a357cb211b618adfef4fa82fc0de3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/15291164b22a357cb211b618adfef4fa82fc0de3 | jbd2: clear BH_Delay & BH_Unwritten in journal_unmap_buffer
journal_unmap_buffer()'s zap_buffer: code clears a lot of buffer head
state ala discard_buffer(), but does not touch _Delay or _Unwritten as
discard_buffer() does.
This can be problematic in some areas of the ext4 code which assume
that if they have found a ... | 0 | void jbd2_journal_unlock_updates (journal_t *journal)
{
J_ASSERT(journal->j_barrier_count != 0);
mutex_unlock(&journal->j_barrier);
write_lock(&journal->j_state_lock);
--journal->j_barrier_count;
write_unlock(&journal->j_state_lock);
wake_up(&journal->j_wait_transaction_locked);
}
| 168,113,347,243,784,280,000,000,000,000,000,000,000 | transaction.c | 312,279,320,265,495,400,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-4086 | The journal_unmap_buffer function in fs/jbd2/transaction.c in the Linux kernel before 3.3.1 does not properly handle the _Delay and _Unwritten buffer head states, which allows local users to cause a denial of service (system crash) by leveraging the presence of an ext4 filesystem that was mounted with a journal. | https://nvd.nist.gov/vuln/detail/CVE-2011-4086 |
26,728 | linux | 15291164b22a357cb211b618adfef4fa82fc0de3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/15291164b22a357cb211b618adfef4fa82fc0de3 | jbd2: clear BH_Delay & BH_Unwritten in journal_unmap_buffer
journal_unmap_buffer()'s zap_buffer: code clears a lot of buffer head
state ala discard_buffer(), but does not touch _Delay or _Unwritten as
discard_buffer() does.
This can be problematic in some areas of the ext4 code which assume
that if they have found a ... | 0 | static handle_t *new_handle(int nblocks)
{
handle_t *handle = jbd2_alloc_handle(GFP_NOFS);
if (!handle)
return NULL;
memset(handle, 0, sizeof(*handle));
handle->h_buffer_credits = nblocks;
handle->h_ref = 1;
lockdep_init_map(&handle->h_lockdep_map, "jbd2_handle",
&jbd2_handle_key, 0);
return handle;
}
| 250,994,719,753,588,040,000,000,000,000,000,000,000 | transaction.c | 312,279,320,265,495,400,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-4086 | The journal_unmap_buffer function in fs/jbd2/transaction.c in the Linux kernel before 3.3.1 does not properly handle the _Delay and _Unwritten buffer head states, which allows local users to cause a denial of service (system crash) by leveraging the presence of an ext4 filesystem that was mounted with a journal. | https://nvd.nist.gov/vuln/detail/CVE-2011-4086 |
26,729 | linux | 15291164b22a357cb211b618adfef4fa82fc0de3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/15291164b22a357cb211b618adfef4fa82fc0de3 | jbd2: clear BH_Delay & BH_Unwritten in journal_unmap_buffer
journal_unmap_buffer()'s zap_buffer: code clears a lot of buffer head
state ala discard_buffer(), but does not touch _Delay or _Unwritten as
discard_buffer() does.
This can be problematic in some areas of the ext4 code which assume
that if they have found a ... | 0 | static inline void update_t_max_wait(transaction_t *transaction,
unsigned long ts)
{
#ifdef CONFIG_JBD2_DEBUG
if (jbd2_journal_enable_debug &&
time_after(transaction->t_start, ts)) {
ts = jbd2_time_diff(ts, transaction->t_start);
spin_lock(&transaction->t_handle_lock);
if (ts > transaction->t_max_w... | 281,141,654,000,633,600,000,000,000,000,000,000,000 | transaction.c | 312,279,320,265,495,400,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-4086 | The journal_unmap_buffer function in fs/jbd2/transaction.c in the Linux kernel before 3.3.1 does not properly handle the _Delay and _Unwritten buffer head states, which allows local users to cause a denial of service (system crash) by leveraging the presence of an ext4 filesystem that was mounted with a journal. | https://nvd.nist.gov/vuln/detail/CVE-2011-4086 |
26,730 | linux | 15291164b22a357cb211b618adfef4fa82fc0de3 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/15291164b22a357cb211b618adfef4fa82fc0de3 | jbd2: clear BH_Delay & BH_Unwritten in journal_unmap_buffer
journal_unmap_buffer()'s zap_buffer: code clears a lot of buffer head
state ala discard_buffer(), but does not touch _Delay or _Unwritten as
discard_buffer() does.
This can be problematic in some areas of the ext4 code which assume
that if they have found a ... | 0 | static void warn_dirty_buffer(struct buffer_head *bh)
{
char b[BDEVNAME_SIZE];
printk(KERN_WARNING
"JBD2: Spotted dirty metadata buffer (dev = %s, blocknr = %llu). "
"There's a risk of filesystem corruption in case of system "
"crash.\n",
bdevname(bh->b_bdev, b), (unsigned long long)b... | 104,787,163,422,743,920,000,000,000,000,000,000,000 | transaction.c | 312,279,320,265,495,400,000,000,000,000,000,000,000 | [
"CWE-119"
] | CVE-2011-4086 | The journal_unmap_buffer function in fs/jbd2/transaction.c in the Linux kernel before 3.3.1 does not properly handle the _Delay and _Unwritten buffer head states, which allows local users to cause a denial of service (system crash) by leveraging the presence of an ext4 filesystem that was mounted with a journal. | https://nvd.nist.gov/vuln/detail/CVE-2011-4086 |
26,731 | linux | 7ed47b7d142ec99ad6880bbbec51e9f12b3af74c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7ed47b7d142ec99ad6880bbbec51e9f12b3af74c | crypto: ghash - Avoid null pointer dereference if no key is set
The ghash_update function passes a pointer to gf128mul_4k_lle which will
be NULL if ghash_setkey is not called or if the most recent call to
ghash_setkey failed to allocate memory. This causes an oops. Fix this
up by returning an error code in the null ... | 0 | static void ghash_exit_tfm(struct crypto_tfm *tfm)
{
struct ghash_ctx *ctx = crypto_tfm_ctx(tfm);
if (ctx->gf128)
gf128mul_free_4k(ctx->gf128);
}
| 295,461,239,678,770,960,000,000,000,000,000,000,000 | ghash-generic.c | 49,675,872,446,992,350,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2011-4081 | crypto/ghash-generic.c in the Linux kernel before 3.1 allows local users to cause a denial of service (NULL pointer dereference and OOPS) or possibly have unspecified other impact by triggering a failed or missing ghash_setkey function call, followed by a (1) ghash_update function call or (2) ghash_final function call,... | https://nvd.nist.gov/vuln/detail/CVE-2011-4081 |
26,732 | linux | 7ed47b7d142ec99ad6880bbbec51e9f12b3af74c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7ed47b7d142ec99ad6880bbbec51e9f12b3af74c | crypto: ghash - Avoid null pointer dereference if no key is set
The ghash_update function passes a pointer to gf128mul_4k_lle which will
be NULL if ghash_setkey is not called or if the most recent call to
ghash_setkey failed to allocate memory. This causes an oops. Fix this
up by returning an error code in the null ... | 0 | static void ghash_flush(struct ghash_ctx *ctx, struct ghash_desc_ctx *dctx)
{
u8 *dst = dctx->buffer;
if (dctx->bytes) {
u8 *tmp = dst + (GHASH_BLOCK_SIZE - dctx->bytes);
while (dctx->bytes--)
*tmp++ ^= 0;
gf128mul_4k_lle((be128 *)dst, ctx->gf128);
}
dctx->bytes = 0;
}
| 100,730,092,566,092,200,000,000,000,000,000,000,000 | ghash-generic.c | 49,675,872,446,992,350,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2011-4081 | crypto/ghash-generic.c in the Linux kernel before 3.1 allows local users to cause a denial of service (NULL pointer dereference and OOPS) or possibly have unspecified other impact by triggering a failed or missing ghash_setkey function call, followed by a (1) ghash_update function call or (2) ghash_final function call,... | https://nvd.nist.gov/vuln/detail/CVE-2011-4081 |
26,733 | linux | 7ed47b7d142ec99ad6880bbbec51e9f12b3af74c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7ed47b7d142ec99ad6880bbbec51e9f12b3af74c | crypto: ghash - Avoid null pointer dereference if no key is set
The ghash_update function passes a pointer to gf128mul_4k_lle which will
be NULL if ghash_setkey is not called or if the most recent call to
ghash_setkey failed to allocate memory. This causes an oops. Fix this
up by returning an error code in the null ... | 0 | static void __exit ghash_mod_exit(void)
{
crypto_unregister_shash(&ghash_alg);
}
| 111,466,627,943,435,950,000,000,000,000,000,000,000 | ghash-generic.c | 49,675,872,446,992,350,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2011-4081 | crypto/ghash-generic.c in the Linux kernel before 3.1 allows local users to cause a denial of service (NULL pointer dereference and OOPS) or possibly have unspecified other impact by triggering a failed or missing ghash_setkey function call, followed by a (1) ghash_update function call or (2) ghash_final function call,... | https://nvd.nist.gov/vuln/detail/CVE-2011-4081 |
26,734 | linux | 7ed47b7d142ec99ad6880bbbec51e9f12b3af74c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7ed47b7d142ec99ad6880bbbec51e9f12b3af74c | crypto: ghash - Avoid null pointer dereference if no key is set
The ghash_update function passes a pointer to gf128mul_4k_lle which will
be NULL if ghash_setkey is not called or if the most recent call to
ghash_setkey failed to allocate memory. This causes an oops. Fix this
up by returning an error code in the null ... | 0 | static int __init ghash_mod_init(void)
{
return crypto_register_shash(&ghash_alg);
}
| 212,870,403,603,325,480,000,000,000,000,000,000,000 | ghash-generic.c | 49,675,872,446,992,350,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2011-4081 | crypto/ghash-generic.c in the Linux kernel before 3.1 allows local users to cause a denial of service (NULL pointer dereference and OOPS) or possibly have unspecified other impact by triggering a failed or missing ghash_setkey function call, followed by a (1) ghash_update function call or (2) ghash_final function call,... | https://nvd.nist.gov/vuln/detail/CVE-2011-4081 |
26,735 | linux | 7ed47b7d142ec99ad6880bbbec51e9f12b3af74c | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/7ed47b7d142ec99ad6880bbbec51e9f12b3af74c | crypto: ghash - Avoid null pointer dereference if no key is set
The ghash_update function passes a pointer to gf128mul_4k_lle which will
be NULL if ghash_setkey is not called or if the most recent call to
ghash_setkey failed to allocate memory. This causes an oops. Fix this
up by returning an error code in the null ... | 0 | static int ghash_setkey(struct crypto_shash *tfm,
const u8 *key, unsigned int keylen)
{
struct ghash_ctx *ctx = crypto_shash_ctx(tfm);
if (keylen != GHASH_BLOCK_SIZE) {
crypto_shash_set_flags(tfm, CRYPTO_TFM_RES_BAD_KEY_LEN);
return -EINVAL;
}
if (ctx->gf128)
gf128mul_free_4k(ctx->gf128);
ctx->gf128 = g... | 133,840,561,233,235,950,000,000,000,000,000,000,000 | ghash-generic.c | 49,675,872,446,992,350,000,000,000,000,000,000,000 | [
"CWE-476"
] | CVE-2011-4081 | crypto/ghash-generic.c in the Linux kernel before 3.1 allows local users to cause a denial of service (NULL pointer dereference and OOPS) or possibly have unspecified other impact by triggering a failed or missing ghash_setkey function call, followed by a (1) ghash_update function call or (2) ghash_final function call,... | https://nvd.nist.gov/vuln/detail/CVE-2011-4081 |
26,788 | linux | 76597cd31470fa130784c78fadb4dab2e624a723 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/76597cd31470fa130784c78fadb4dab2e624a723 | proc: fix oops on invalid /proc/<pid>/maps access
When m_start returns an error, the seq_file logic will still call m_stop
with that error entry, so we'd better make sure that we check it before
using it as a vma.
Introduced by commit ec6fd8a4355c ("report errors in /proc/*/*map*
sanely"), which replaced NULL with va... | 0 | static int clear_refs_pte_range(pmd_t *pmd, unsigned long addr,
unsigned long end, struct mm_walk *walk)
{
struct vm_area_struct *vma = walk->private;
pte_t *pte, ptent;
spinlock_t *ptl;
struct page *page;
split_huge_page_pmd(walk->mm, pmd);
pte = pte_offset_map_lock(vma->vm_mm, pmd, addr, &ptl);
for (; ad... | 170,607,622,136,954,400,000,000,000,000,000,000,000 | task_mmu.c | 544,927,168,925,675,800,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-3637 | The m_stop function in fs/proc/task_mmu.c in the Linux kernel before 2.6.39 allows local users to cause a denial of service (OOPS) via vectors that trigger an m_start error. | https://nvd.nist.gov/vuln/detail/CVE-2011-3637 |
26,789 | linux | 76597cd31470fa130784c78fadb4dab2e624a723 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/76597cd31470fa130784c78fadb4dab2e624a723 | proc: fix oops on invalid /proc/<pid>/maps access
When m_start returns an error, the seq_file logic will still call m_stop
with that error entry, so we'd better make sure that we check it before
using it as a vma.
Introduced by commit ec6fd8a4355c ("report errors in /proc/*/*map*
sanely"), which replaced NULL with va... | 0 | static ssize_t clear_refs_write(struct file *file, const char __user *buf,
size_t count, loff_t *ppos)
{
struct task_struct *task;
char buffer[PROC_NUMBUF];
struct mm_struct *mm;
struct vm_area_struct *vma;
long type;
memset(buffer, 0, sizeof(buffer));
if (count > sizeof(buffer) - 1)
count = sizeof(buffer... | 282,360,309,862,382,040,000,000,000,000,000,000,000 | task_mmu.c | 544,927,168,925,675,800,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-3637 | The m_stop function in fs/proc/task_mmu.c in the Linux kernel before 2.6.39 allows local users to cause a denial of service (OOPS) via vectors that trigger an m_start error. | https://nvd.nist.gov/vuln/detail/CVE-2011-3637 |
26,790 | linux | 76597cd31470fa130784c78fadb4dab2e624a723 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/76597cd31470fa130784c78fadb4dab2e624a723 | proc: fix oops on invalid /proc/<pid>/maps access
When m_start returns an error, the seq_file logic will still call m_stop
with that error entry, so we'd better make sure that we check it before
using it as a vma.
Introduced by commit ec6fd8a4355c ("report errors in /proc/*/*map*
sanely"), which replaced NULL with va... | 0 | static int numa_maps_open(struct inode *inode, struct file *file)
{
return do_maps_open(inode, file, &proc_pid_numa_maps_op);
}
| 334,796,488,307,640,200,000,000,000,000,000,000,000 | task_mmu.c | 180,717,601,192,202,440,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-3637 | The m_stop function in fs/proc/task_mmu.c in the Linux kernel before 2.6.39 allows local users to cause a denial of service (OOPS) via vectors that trigger an m_start error. | https://nvd.nist.gov/vuln/detail/CVE-2011-3637 |
26,791 | linux | 76597cd31470fa130784c78fadb4dab2e624a723 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/76597cd31470fa130784c78fadb4dab2e624a723 | proc: fix oops on invalid /proc/<pid>/maps access
When m_start returns an error, the seq_file logic will still call m_stop
with that error entry, so we'd better make sure that we check it before
using it as a vma.
Introduced by commit ec6fd8a4355c ("report errors in /proc/*/*map*
sanely"), which replaced NULL with va... | 0 | static ssize_t pagemap_read(struct file *file, char __user *buf,
size_t count, loff_t *ppos)
{
struct task_struct *task = get_proc_task(file->f_path.dentry->d_inode);
struct mm_struct *mm;
struct pagemapread pm;
int ret = -ESRCH;
struct mm_walk pagemap_walk = {};
unsigned long src;
unsigned long svpfn;
u... | 273,673,961,553,970,300,000,000,000,000,000,000,000 | task_mmu.c | 544,927,168,925,675,800,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-3637 | The m_stop function in fs/proc/task_mmu.c in the Linux kernel before 2.6.39 allows local users to cause a denial of service (OOPS) via vectors that trigger an m_start error. | https://nvd.nist.gov/vuln/detail/CVE-2011-3637 |
26,792 | linux | 76597cd31470fa130784c78fadb4dab2e624a723 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/76597cd31470fa130784c78fadb4dab2e624a723 | proc: fix oops on invalid /proc/<pid>/maps access
When m_start returns an error, the seq_file logic will still call m_stop
with that error entry, so we'd better make sure that we check it before
using it as a vma.
Introduced by commit ec6fd8a4355c ("report errors in /proc/*/*map*
sanely"), which replaced NULL with va... | 0 | static void show_map_vma(struct seq_file *m, struct vm_area_struct *vma)
{
struct mm_struct *mm = vma->vm_mm;
struct file *file = vma->vm_file;
int flags = vma->vm_flags;
unsigned long ino = 0;
unsigned long long pgoff = 0;
unsigned long start;
dev_t dev = 0;
int len;
if (file) {
struct inode *inode = vma->... | 333,352,891,235,255,440,000,000,000,000,000,000,000 | task_mmu.c | 544,927,168,925,675,800,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-3637 | The m_stop function in fs/proc/task_mmu.c in the Linux kernel before 2.6.39 allows local users to cause a denial of service (OOPS) via vectors that trigger an m_start error. | https://nvd.nist.gov/vuln/detail/CVE-2011-3637 |
26,793 | linux | 70945643722ffeac779d2529a348f99567fa5c33 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/70945643722ffeac779d2529a348f99567fa5c33 | cifs: always do is_path_accessible check in cifs_mount
Currently, we skip doing the is_path_accessible check in cifs_mount if
there is no prefixpath. I have a report of at least one server however
that allows a TREE_CONNECT to a share that has a DFS referral at its
root. The reporter in this case was using a UNC that ... | 0 | CIFSTCon(unsigned int xid, struct cifsSesInfo *ses,
const char *tree, struct cifsTconInfo *tcon,
const struct nls_table *nls_codepage)
{
struct smb_hdr *smb_buffer;
struct smb_hdr *smb_buffer_response;
TCONX_REQ *pSMB;
TCONX_RSP *pSMBr;
unsigned char *bcc_ptr;
int rc = 0;
int length;
__u16 bytes_left, count... | 148,547,755,181,087,400,000,000,000,000,000,000,000 | connect.c | 332,227,986,165,163,880,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-3363 | The setup_cifs_sb function in fs/cifs/connect.c in the Linux kernel before 2.6.39 does not properly handle DFS referrals, which allows remote CIFS servers to cause a denial of service (system crash) by placing a referral at the root of a share. | https://nvd.nist.gov/vuln/detail/CVE-2011-3363 |
26,794 | linux | 70945643722ffeac779d2529a348f99567fa5c33 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/70945643722ffeac779d2529a348f99567fa5c33 | cifs: always do is_path_accessible check in cifs_mount
Currently, we skip doing the is_path_accessible check in cifs_mount if
there is no prefixpath. I have a report of at least one server however
that allows a TREE_CONNECT to a share that has a DFS referral at its
root. The reporter in this case was using a UNC that ... | 0 | bind_socket(struct TCP_Server_Info *server)
{
int rc = 0;
if (server->srcaddr.ss_family != AF_UNSPEC) {
/* Bind to the specified local IP address */
struct socket *socket = server->ssocket;
rc = socket->ops->bind(socket,
(struct sockaddr *) &server->srcaddr,
sizeof(server->srcaddr));
if ... | 68,836,434,368,111,360,000,000,000,000,000,000,000 | connect.c | 332,227,986,165,163,880,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-3363 | The setup_cifs_sb function in fs/cifs/connect.c in the Linux kernel before 2.6.39 does not properly handle DFS referrals, which allows remote CIFS servers to cause a denial of service (system crash) by placing a referral at the root of a share. | https://nvd.nist.gov/vuln/detail/CVE-2011-3363 |
26,795 | linux | 70945643722ffeac779d2529a348f99567fa5c33 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/70945643722ffeac779d2529a348f99567fa5c33 | cifs: always do is_path_accessible check in cifs_mount
Currently, we skip doing the is_path_accessible check in cifs_mount if
there is no prefixpath. I have a report of at least one server however
that allows a TREE_CONNECT to a share that has a DFS referral at its
root. The reporter in this case was using a UNC that ... | 0 | build_unc_path_to_root(const struct smb_vol *volume_info,
const struct cifs_sb_info *cifs_sb)
{
char *full_path;
int unc_len = strnlen(volume_info->UNC, MAX_TREE_SIZE + 1);
full_path = kmalloc(unc_len + cifs_sb->prepathlen + 1, GFP_KERNEL);
if (full_path == NULL)
return ERR_PTR(-ENOMEM);
strncpy(full_path, v... | 244,282,721,959,487,400,000,000,000,000,000,000,000 | connect.c | 259,629,772,591,307,700,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-3363 | The setup_cifs_sb function in fs/cifs/connect.c in the Linux kernel before 2.6.39 does not properly handle DFS referrals, which allows remote CIFS servers to cause a denial of service (system crash) by placing a referral at the root of a share. | https://nvd.nist.gov/vuln/detail/CVE-2011-3363 |
26,796 | linux | 70945643722ffeac779d2529a348f99567fa5c33 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/70945643722ffeac779d2529a348f99567fa5c33 | cifs: always do is_path_accessible check in cifs_mount
Currently, we skip doing the is_path_accessible check in cifs_mount if
there is no prefixpath. I have a report of at least one server however
that allows a TREE_CONNECT to a share that has a DFS referral at its
root. The reporter in this case was using a UNC that ... | 0 | static int check2ndT2(struct smb_hdr *pSMB, unsigned int maxBufSize)
{
struct smb_t2_rsp *pSMBt;
int remaining;
__u16 total_data_size, data_in_this_rsp;
if (pSMB->Command != SMB_COM_TRANSACTION2)
return 0;
/* check for plausible wct, bcc and t2 data and parm sizes */
/* check for parm and data offset going be... | 94,265,620,762,657,790,000,000,000,000,000,000,000 | connect.c | 332,227,986,165,163,880,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-3363 | The setup_cifs_sb function in fs/cifs/connect.c in the Linux kernel before 2.6.39 does not properly handle DFS referrals, which allows remote CIFS servers to cause a denial of service (system crash) by placing a referral at the root of a share. | https://nvd.nist.gov/vuln/detail/CVE-2011-3363 |
26,797 | linux | 70945643722ffeac779d2529a348f99567fa5c33 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/70945643722ffeac779d2529a348f99567fa5c33 | cifs: always do is_path_accessible check in cifs_mount
Currently, we skip doing the is_path_accessible check in cifs_mount if
there is no prefixpath. I have a report of at least one server however
that allows a TREE_CONNECT to a share that has a DFS referral at its
root. The reporter in this case was using a UNC that ... | 0 | cifs_construct_tcon(struct cifs_sb_info *cifs_sb, uid_t fsuid)
{
struct cifsTconInfo *master_tcon = cifs_sb_master_tcon(cifs_sb);
struct cifsSesInfo *ses;
struct cifsTconInfo *tcon = NULL;
struct smb_vol *vol_info;
char username[MAX_USERNAME_SIZE + 1];
vol_info = kzalloc(sizeof(*vol_info), GFP_KERNEL);
if (vol_... | 322,990,579,219,374,530,000,000,000,000,000,000,000 | connect.c | 332,227,986,165,163,880,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-3363 | The setup_cifs_sb function in fs/cifs/connect.c in the Linux kernel before 2.6.39 does not properly handle DFS referrals, which allows remote CIFS servers to cause a denial of service (system crash) by placing a referral at the root of a share. | https://nvd.nist.gov/vuln/detail/CVE-2011-3363 |
26,798 | linux | 70945643722ffeac779d2529a348f99567fa5c33 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/70945643722ffeac779d2529a348f99567fa5c33 | cifs: always do is_path_accessible check in cifs_mount
Currently, we skip doing the is_path_accessible check in cifs_mount if
there is no prefixpath. I have a report of at least one server however
that allows a TREE_CONNECT to a share that has a DFS referral at its
root. The reporter in this case was using a UNC that ... | 0 | cifs_demultiplex_thread(struct TCP_Server_Info *server)
{
int length;
unsigned int pdu_length, total_read;
struct smb_hdr *smb_buffer = NULL;
struct smb_hdr *bigbuf = NULL;
struct smb_hdr *smallbuf = NULL;
struct msghdr smb_msg;
struct kvec iov;
struct socket *csocket = server->ssocket;
struct list_head *tmp, ... | 195,506,167,575,625,400,000,000,000,000,000,000,000 | connect.c | 332,227,986,165,163,880,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-3363 | The setup_cifs_sb function in fs/cifs/connect.c in the Linux kernel before 2.6.39 does not properly handle DFS referrals, which allows remote CIFS servers to cause a denial of service (system crash) by placing a referral at the root of a share. | https://nvd.nist.gov/vuln/detail/CVE-2011-3363 |
26,799 | linux | 70945643722ffeac779d2529a348f99567fa5c33 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/70945643722ffeac779d2529a348f99567fa5c33 | cifs: always do is_path_accessible check in cifs_mount
Currently, we skip doing the is_path_accessible check in cifs_mount if
there is no prefixpath. I have a report of at least one server however
that allows a TREE_CONNECT to a share that has a DFS referral at its
root. The reporter in this case was using a UNC that ... | 0 | cifs_echo_request(struct work_struct *work)
{
int rc;
struct TCP_Server_Info *server = container_of(work,
struct TCP_Server_Info, echo.work);
/*
* We cannot send an echo until the NEGOTIATE_PROTOCOL request is
* done, which is indicated by maxBuf != 0. Also, no need to ping if
* we got a response recentl... | 289,999,363,170,135,200,000,000,000,000,000,000,000 | connect.c | 332,227,986,165,163,880,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-3363 | The setup_cifs_sb function in fs/cifs/connect.c in the Linux kernel before 2.6.39 does not properly handle DFS referrals, which allows remote CIFS servers to cause a denial of service (system crash) by placing a referral at the root of a share. | https://nvd.nist.gov/vuln/detail/CVE-2011-3363 |
26,800 | linux | 70945643722ffeac779d2529a348f99567fa5c33 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/70945643722ffeac779d2529a348f99567fa5c33 | cifs: always do is_path_accessible check in cifs_mount
Currently, we skip doing the is_path_accessible check in cifs_mount if
there is no prefixpath. I have a report of at least one server however
that allows a TREE_CONNECT to a share that has a DFS referral at its
root. The reporter in this case was using a UNC that ... | 0 | cifs_find_smb_ses(struct TCP_Server_Info *server, struct smb_vol *vol)
{
struct cifsSesInfo *ses;
spin_lock(&cifs_tcp_ses_lock);
list_for_each_entry(ses, &server->smb_ses_list, smb_ses_list) {
switch (server->secType) {
case Kerberos:
if (vol->cred_uid != ses->cred_uid)
continue;
break;
default:
... | 165,497,877,886,831,370,000,000,000,000,000,000,000 | connect.c | 332,227,986,165,163,880,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-3363 | The setup_cifs_sb function in fs/cifs/connect.c in the Linux kernel before 2.6.39 does not properly handle DFS referrals, which allows remote CIFS servers to cause a denial of service (system crash) by placing a referral at the root of a share. | https://nvd.nist.gov/vuln/detail/CVE-2011-3363 |
26,801 | linux | 70945643722ffeac779d2529a348f99567fa5c33 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/70945643722ffeac779d2529a348f99567fa5c33 | cifs: always do is_path_accessible check in cifs_mount
Currently, we skip doing the is_path_accessible check in cifs_mount if
there is no prefixpath. I have a report of at least one server however
that allows a TREE_CONNECT to a share that has a DFS referral at its
root. The reporter in this case was using a UNC that ... | 0 | cifs_find_tcon(struct cifsSesInfo *ses, const char *unc)
{
struct list_head *tmp;
struct cifsTconInfo *tcon;
spin_lock(&cifs_tcp_ses_lock);
list_for_each(tmp, &ses->tcon_list) {
tcon = list_entry(tmp, struct cifsTconInfo, tcon_list);
if (tcon->tidStatus == CifsExiting)
continue;
if (strncmp(tcon->treeName... | 319,454,101,065,236,450,000,000,000,000,000,000,000 | connect.c | 332,227,986,165,163,880,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-3363 | The setup_cifs_sb function in fs/cifs/connect.c in the Linux kernel before 2.6.39 does not properly handle DFS referrals, which allows remote CIFS servers to cause a denial of service (system crash) by placing a referral at the root of a share. | https://nvd.nist.gov/vuln/detail/CVE-2011-3363 |
26,802 | linux | 70945643722ffeac779d2529a348f99567fa5c33 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/70945643722ffeac779d2529a348f99567fa5c33 | cifs: always do is_path_accessible check in cifs_mount
Currently, we skip doing the is_path_accessible check in cifs_mount if
there is no prefixpath. I have a report of at least one server however
that allows a TREE_CONNECT to a share that has a DFS referral at its
root. The reporter in this case was using a UNC that ... | 0 | cifs_find_tcp_session(struct sockaddr *addr, struct smb_vol *vol)
{
struct TCP_Server_Info *server;
spin_lock(&cifs_tcp_ses_lock);
list_for_each_entry(server, &cifs_tcp_ses_list, tcp_ses_list) {
if (!net_eq(cifs_net_ns(server), current->nsproxy->net_ns))
continue;
if (!match_address(server, addr,
(st... | 270,197,400,751,810,640,000,000,000,000,000,000,000 | connect.c | 332,227,986,165,163,880,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-3363 | The setup_cifs_sb function in fs/cifs/connect.c in the Linux kernel before 2.6.39 does not properly handle DFS referrals, which allows remote CIFS servers to cause a denial of service (system crash) by placing a referral at the root of a share. | https://nvd.nist.gov/vuln/detail/CVE-2011-3363 |
26,803 | linux | 70945643722ffeac779d2529a348f99567fa5c33 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/70945643722ffeac779d2529a348f99567fa5c33 | cifs: always do is_path_accessible check in cifs_mount
Currently, we skip doing the is_path_accessible check in cifs_mount if
there is no prefixpath. I have a report of at least one server however
that allows a TREE_CONNECT to a share that has a DFS referral at its
root. The reporter in this case was using a UNC that ... | 0 | cifs_get_smb_ses(struct TCP_Server_Info *server, struct smb_vol *volume_info)
{
int rc = -ENOMEM, xid;
struct cifsSesInfo *ses;
struct sockaddr_in *addr = (struct sockaddr_in *)&server->dstaddr;
struct sockaddr_in6 *addr6 = (struct sockaddr_in6 *)&server->dstaddr;
xid = GetXid();
ses = cifs_find_smb_ses(server,... | 193,671,398,523,717,550,000,000,000,000,000,000,000 | connect.c | 332,227,986,165,163,880,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-3363 | The setup_cifs_sb function in fs/cifs/connect.c in the Linux kernel before 2.6.39 does not properly handle DFS referrals, which allows remote CIFS servers to cause a denial of service (system crash) by placing a referral at the root of a share. | https://nvd.nist.gov/vuln/detail/CVE-2011-3363 |
26,804 | linux | 70945643722ffeac779d2529a348f99567fa5c33 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/70945643722ffeac779d2529a348f99567fa5c33 | cifs: always do is_path_accessible check in cifs_mount
Currently, we skip doing the is_path_accessible check in cifs_mount if
there is no prefixpath. I have a report of at least one server however
that allows a TREE_CONNECT to a share that has a DFS referral at its
root. The reporter in this case was using a UNC that ... | 0 | cifs_get_tcon(struct cifsSesInfo *ses, struct smb_vol *volume_info)
{
int rc, xid;
struct cifsTconInfo *tcon;
tcon = cifs_find_tcon(ses, volume_info->UNC);
if (tcon) {
cFYI(1, "Found match on UNC path");
/* existing tcon already has a reference */
cifs_put_smb_ses(ses);
if (tcon->seal != volume_info->seal)... | 260,834,606,119,790,080,000,000,000,000,000,000,000 | connect.c | 332,227,986,165,163,880,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-3363 | The setup_cifs_sb function in fs/cifs/connect.c in the Linux kernel before 2.6.39 does not properly handle DFS referrals, which allows remote CIFS servers to cause a denial of service (system crash) by placing a referral at the root of a share. | https://nvd.nist.gov/vuln/detail/CVE-2011-3363 |
26,805 | linux | 70945643722ffeac779d2529a348f99567fa5c33 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/70945643722ffeac779d2529a348f99567fa5c33 | cifs: always do is_path_accessible check in cifs_mount
Currently, we skip doing the is_path_accessible check in cifs_mount if
there is no prefixpath. I have a report of at least one server however
that allows a TREE_CONNECT to a share that has a DFS referral at its
root. The reporter in this case was using a UNC that ... | 0 | cifs_get_tcp_session(struct smb_vol *volume_info)
{
struct TCP_Server_Info *tcp_ses = NULL;
struct sockaddr_storage addr;
struct sockaddr_in *sin_server = (struct sockaddr_in *) &addr;
struct sockaddr_in6 *sin_server6 = (struct sockaddr_in6 *) &addr;
int rc;
memset(&addr, 0, sizeof(struct sockaddr_storage));
c... | 3,169,691,296,881,441,000,000,000,000,000,000,000 | connect.c | 332,227,986,165,163,880,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-3363 | The setup_cifs_sb function in fs/cifs/connect.c in the Linux kernel before 2.6.39 does not properly handle DFS referrals, which allows remote CIFS servers to cause a denial of service (system crash) by placing a referral at the root of a share. | https://nvd.nist.gov/vuln/detail/CVE-2011-3363 |
26,806 | linux | 70945643722ffeac779d2529a348f99567fa5c33 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/70945643722ffeac779d2529a348f99567fa5c33 | cifs: always do is_path_accessible check in cifs_mount
Currently, we skip doing the is_path_accessible check in cifs_mount if
there is no prefixpath. I have a report of at least one server however
that allows a TREE_CONNECT to a share that has a DFS referral at its
root. The reporter in this case was using a UNC that ... | 0 | int cifs_negotiate_protocol(unsigned int xid, struct cifsSesInfo *ses)
{
int rc = 0;
struct TCP_Server_Info *server = ses->server;
/* only send once per connect */
if (server->maxBuf != 0)
return 0;
rc = CIFSSMBNegotiate(xid, ses);
if (rc == -EAGAIN) {
/* retry only once on 1st time connection */
rc = CIF... | 14,291,332,965,638,880,000,000,000,000,000,000,000 | connect.c | 259,629,772,591,307,700,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-3363 | The setup_cifs_sb function in fs/cifs/connect.c in the Linux kernel before 2.6.39 does not properly handle DFS referrals, which allows remote CIFS servers to cause a denial of service (system crash) by placing a referral at the root of a share. | https://nvd.nist.gov/vuln/detail/CVE-2011-3363 |
26,807 | linux | 70945643722ffeac779d2529a348f99567fa5c33 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/70945643722ffeac779d2529a348f99567fa5c33 | cifs: always do is_path_accessible check in cifs_mount
Currently, we skip doing the is_path_accessible check in cifs_mount if
there is no prefixpath. I have a report of at least one server however
that allows a TREE_CONNECT to a share that has a DFS referral at its
root. The reporter in this case was using a UNC that ... | 0 | cifs_parse_mount_options(char *options, const char *devname,
struct smb_vol *vol)
{
char *value;
char *data;
unsigned int temp_len, i, j;
char separator[2];
short int override_uid = -1;
short int override_gid = -1;
bool uid_specified = false;
bool gid_specified = false;
char *nodename = utsname()->nodenam... | 102,464,968,215,347,780,000,000,000,000,000,000,000 | connect.c | 332,227,986,165,163,880,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-3363 | The setup_cifs_sb function in fs/cifs/connect.c in the Linux kernel before 2.6.39 does not properly handle DFS referrals, which allows remote CIFS servers to cause a denial of service (system crash) by placing a referral at the root of a share. | https://nvd.nist.gov/vuln/detail/CVE-2011-3363 |
26,808 | linux | 70945643722ffeac779d2529a348f99567fa5c33 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/70945643722ffeac779d2529a348f99567fa5c33 | cifs: always do is_path_accessible check in cifs_mount
Currently, we skip doing the is_path_accessible check in cifs_mount if
there is no prefixpath. I have a report of at least one server however
that allows a TREE_CONNECT to a share that has a DFS referral at its
root. The reporter in this case was using a UNC that ... | 0 | cifs_prune_tlinks(struct work_struct *work)
{
struct cifs_sb_info *cifs_sb = container_of(work, struct cifs_sb_info,
prune_tlinks.work);
struct rb_root *root = &cifs_sb->tlink_tree;
struct rb_node *node = rb_first(root);
struct rb_node *tmp;
struct tcon_link *tlink;
/*
* Because we drop the spinlock ... | 27,692,147,687,643,897,000,000,000,000,000,000,000 | connect.c | 332,227,986,165,163,880,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-3363 | The setup_cifs_sb function in fs/cifs/connect.c in the Linux kernel before 2.6.39 does not properly handle DFS referrals, which allows remote CIFS servers to cause a denial of service (system crash) by placing a referral at the root of a share. | https://nvd.nist.gov/vuln/detail/CVE-2011-3363 |
26,809 | linux | 70945643722ffeac779d2529a348f99567fa5c33 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/70945643722ffeac779d2529a348f99567fa5c33 | cifs: always do is_path_accessible check in cifs_mount
Currently, we skip doing the is_path_accessible check in cifs_mount if
there is no prefixpath. I have a report of at least one server however
that allows a TREE_CONNECT to a share that has a DFS referral at its
root. The reporter in this case was using a UNC that ... | 0 | cifs_put_smb_ses(struct cifsSesInfo *ses)
{
int xid;
struct TCP_Server_Info *server = ses->server;
cFYI(1, "%s: ses_count=%d\n", __func__, ses->ses_count);
spin_lock(&cifs_tcp_ses_lock);
if (--ses->ses_count > 0) {
spin_unlock(&cifs_tcp_ses_lock);
return;
}
list_del_init(&ses->smb_ses_list);
spin_unlock(&... | 103,618,620,646,393,900,000,000,000,000,000,000,000 | connect.c | 332,227,986,165,163,880,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-3363 | The setup_cifs_sb function in fs/cifs/connect.c in the Linux kernel before 2.6.39 does not properly handle DFS referrals, which allows remote CIFS servers to cause a denial of service (system crash) by placing a referral at the root of a share. | https://nvd.nist.gov/vuln/detail/CVE-2011-3363 |
26,810 | linux | 70945643722ffeac779d2529a348f99567fa5c33 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/70945643722ffeac779d2529a348f99567fa5c33 | cifs: always do is_path_accessible check in cifs_mount
Currently, we skip doing the is_path_accessible check in cifs_mount if
there is no prefixpath. I have a report of at least one server however
that allows a TREE_CONNECT to a share that has a DFS referral at its
root. The reporter in this case was using a UNC that ... | 0 | cifs_put_tcon(struct cifsTconInfo *tcon)
{
int xid;
struct cifsSesInfo *ses = tcon->ses;
cFYI(1, "%s: tc_count=%d\n", __func__, tcon->tc_count);
spin_lock(&cifs_tcp_ses_lock);
if (--tcon->tc_count > 0) {
spin_unlock(&cifs_tcp_ses_lock);
return;
}
list_del_init(&tcon->tcon_list);
spin_unlock(&cifs_tcp_ses_... | 306,464,730,040,810,860,000,000,000,000,000,000,000 | connect.c | 332,227,986,165,163,880,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-3363 | The setup_cifs_sb function in fs/cifs/connect.c in the Linux kernel before 2.6.39 does not properly handle DFS referrals, which allows remote CIFS servers to cause a denial of service (system crash) by placing a referral at the root of a share. | https://nvd.nist.gov/vuln/detail/CVE-2011-3363 |
26,811 | linux | 70945643722ffeac779d2529a348f99567fa5c33 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/70945643722ffeac779d2529a348f99567fa5c33 | cifs: always do is_path_accessible check in cifs_mount
Currently, we skip doing the is_path_accessible check in cifs_mount if
there is no prefixpath. I have a report of at least one server however
that allows a TREE_CONNECT to a share that has a DFS referral at its
root. The reporter in this case was using a UNC that ... | 0 | cifs_put_tcp_session(struct TCP_Server_Info *server)
{
struct task_struct *task;
spin_lock(&cifs_tcp_ses_lock);
if (--server->srv_count > 0) {
spin_unlock(&cifs_tcp_ses_lock);
return;
}
put_net(cifs_net_ns(server));
list_del_init(&server->tcp_ses_list);
spin_unlock(&cifs_tcp_ses_lock);
cancel_delayed_wo... | 225,460,608,379,744,350,000,000,000,000,000,000,000 | connect.c | 332,227,986,165,163,880,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-3363 | The setup_cifs_sb function in fs/cifs/connect.c in the Linux kernel before 2.6.39 does not properly handle DFS referrals, which allows remote CIFS servers to cause a denial of service (system crash) by placing a referral at the root of a share. | https://nvd.nist.gov/vuln/detail/CVE-2011-3363 |
26,812 | linux | 70945643722ffeac779d2529a348f99567fa5c33 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/70945643722ffeac779d2529a348f99567fa5c33 | cifs: always do is_path_accessible check in cifs_mount
Currently, we skip doing the is_path_accessible check in cifs_mount if
there is no prefixpath. I have a report of at least one server however
that allows a TREE_CONNECT to a share that has a DFS referral at its
root. The reporter in this case was using a UNC that ... | 0 | cifs_put_tlink(struct tcon_link *tlink)
{
if (!tlink || IS_ERR(tlink))
return;
if (!atomic_dec_and_test(&tlink->tl_count) ||
test_bit(TCON_LINK_IN_TREE, &tlink->tl_flags)) {
tlink->tl_time = jiffies;
return;
}
if (!IS_ERR(tlink_tcon(tlink)))
cifs_put_tcon(tlink_tcon(tlink));
kfree(tlink);
return;
}... | 58,914,315,149,906,620,000,000,000,000,000,000,000 | connect.c | 332,227,986,165,163,880,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-3363 | The setup_cifs_sb function in fs/cifs/connect.c in the Linux kernel before 2.6.39 does not properly handle DFS referrals, which allows remote CIFS servers to cause a denial of service (system crash) by placing a referral at the root of a share. | https://nvd.nist.gov/vuln/detail/CVE-2011-3363 |
26,813 | linux | 70945643722ffeac779d2529a348f99567fa5c33 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/70945643722ffeac779d2529a348f99567fa5c33 | cifs: always do is_path_accessible check in cifs_mount
Currently, we skip doing the is_path_accessible check in cifs_mount if
there is no prefixpath. I have a report of at least one server however
that allows a TREE_CONNECT to a share that has a DFS referral at its
root. The reporter in this case was using a UNC that ... | 0 | cifs_reclassify_socket4(struct socket *sock)
{
struct sock *sk = sock->sk;
BUG_ON(sock_owned_by_user(sk));
sock_lock_init_class_and_name(sk, "slock-AF_INET-CIFS",
&cifs_slock_key[0], "sk_lock-AF_INET-CIFS", &cifs_key[0]);
}
| 145,853,517,950,278,000,000,000,000,000,000,000,000 | connect.c | 259,629,772,591,307,700,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-3363 | The setup_cifs_sb function in fs/cifs/connect.c in the Linux kernel before 2.6.39 does not properly handle DFS referrals, which allows remote CIFS servers to cause a denial of service (system crash) by placing a referral at the root of a share. | https://nvd.nist.gov/vuln/detail/CVE-2011-3363 |
26,814 | linux | 70945643722ffeac779d2529a348f99567fa5c33 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/70945643722ffeac779d2529a348f99567fa5c33 | cifs: always do is_path_accessible check in cifs_mount
Currently, we skip doing the is_path_accessible check in cifs_mount if
there is no prefixpath. I have a report of at least one server however
that allows a TREE_CONNECT to a share that has a DFS referral at its
root. The reporter in this case was using a UNC that ... | 0 | cifs_reclassify_socket4(struct socket *sock)
{
}
| 39,704,620,509,791,005,000,000,000,000,000,000,000 | connect.c | 259,629,772,591,307,700,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-3363 | The setup_cifs_sb function in fs/cifs/connect.c in the Linux kernel before 2.6.39 does not properly handle DFS referrals, which allows remote CIFS servers to cause a denial of service (system crash) by placing a referral at the root of a share. | https://nvd.nist.gov/vuln/detail/CVE-2011-3363 |
26,815 | linux | 70945643722ffeac779d2529a348f99567fa5c33 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/70945643722ffeac779d2529a348f99567fa5c33 | cifs: always do is_path_accessible check in cifs_mount
Currently, we skip doing the is_path_accessible check in cifs_mount if
there is no prefixpath. I have a report of at least one server however
that allows a TREE_CONNECT to a share that has a DFS referral at its
root. The reporter in this case was using a UNC that ... | 0 | cifs_reclassify_socket6(struct socket *sock)
{
struct sock *sk = sock->sk;
BUG_ON(sock_owned_by_user(sk));
sock_lock_init_class_and_name(sk, "slock-AF_INET6-CIFS",
&cifs_slock_key[1], "sk_lock-AF_INET6-CIFS", &cifs_key[1]);
}
| 182,659,706,205,429,900,000,000,000,000,000,000,000 | connect.c | 259,629,772,591,307,700,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-3363 | The setup_cifs_sb function in fs/cifs/connect.c in the Linux kernel before 2.6.39 does not properly handle DFS referrals, which allows remote CIFS servers to cause a denial of service (system crash) by placing a referral at the root of a share. | https://nvd.nist.gov/vuln/detail/CVE-2011-3363 |
26,816 | linux | 70945643722ffeac779d2529a348f99567fa5c33 | https://github.com/torvalds/linux | https://github.com/torvalds/linux/commit/70945643722ffeac779d2529a348f99567fa5c33 | cifs: always do is_path_accessible check in cifs_mount
Currently, we skip doing the is_path_accessible check in cifs_mount if
there is no prefixpath. I have a report of at least one server however
that allows a TREE_CONNECT to a share that has a DFS referral at its
root. The reporter in this case was using a UNC that ... | 0 | cifs_reclassify_socket6(struct socket *sock)
{
}
| 311,142,205,114,578,220,000,000,000,000,000,000,000 | connect.c | 259,629,772,591,307,700,000,000,000,000,000,000,000 | [
"CWE-20"
] | CVE-2011-3363 | The setup_cifs_sb function in fs/cifs/connect.c in the Linux kernel before 2.6.39 does not properly handle DFS referrals, which allows remote CIFS servers to cause a denial of service (system crash) by placing a referral at the root of a share. | https://nvd.nist.gov/vuln/detail/CVE-2011-3363 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.